[PD] Deken filename too long for certain filesystems (ecryptfs on ext4)

[Roman Haefeli]

Hey all

While trying to install the most recent version of ELSE, Deken simply
reported: "Download failed". I then tried to download with wget which
succeeded, but the resulting file was named (125 characters):

else[v1.0-0_beta45_with_live_electronics_tutorial](Darwin-amd64-32)(Darwin-i386-32)(Linux-amd64-32)(Linux-arm64-32)(Linux-ar

The original filename is much longer (186 chars):

else[v1.0-0_beta45_with_live_electronics_tutorial](Darwin-amd64-32)(Darwin-i386-32)(Linux-amd64-32)(Linux-arm64-32)(Linux-armv6-32)(Linux-i386-32)(Windows-amd64-32)(Windows-i386-32).dek


While many filesystems use a limit of 255 chars for names, mine is bit
more limited. I encrypted my home folder with ecryptfs which is a
userspace filesystem on top of ext4. Because encrypting the filename
requires extra space, the limit of ecryptfs for filenames is lower than
the one of the underlying filesystem (which is ext4 in my case).

I think having a lower limit than the common 255 characters is silly. I
don't think that Deken packages should assume a smaller filename limit
than 255. However, we see that the above example is not that far from
that (support for a few additional archs or double-precision could
reach it). Also, I wanted to share my experience. Maybe it has an
impact on the recent external double-precision file extension
discussion.

Roman

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20220409/b8aaefa7/attachment.sig>