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):
elsev1.0-0_beta45_with_live_electronics_tutorial(Darwin-i386-32)(Linux-amd64-32)(Linux-arm64-32)(Linux-ar
The original filename is much longer (186 chars):
elsev1.0-0_beta45_with_live_electronics_tutorial(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
my library name is longer than it should be but the "extra" stuff only counts 37 characters (beta45_with_live_electronics_tutorial)
and next release should also include the apple silicon extension
I was thinking of a separate batch for double precision
cheers
Em sáb., 9 de abr. de 2022 às 18:50, Roman Haefeli reduzent@gmail.com escreveu:
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):
elsev1.0-0_beta45_with_live_electronics_tutorial(Darwin-i386-32)(Linux-amd64-32)(Linux-arm64-32)(Linux-ar
The original filename is much longer (186 chars):
elsev1.0-0_beta45_with_live_electronics_tutorial(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
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 4/9/22 23:48, Roman Haefeli wrote:
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.
please create a bugreport on https://github.com/pure-data/deken/issues
there is no real reason that the name of the downloaded file must have the full long name.
in the meantime, you can
button) to install the manually downloaded file (alternatively, you could also just drag the .dek file onto the deken window)
when renaming the .dek file, make sure to keep the library-name (esp. if you use the "Try to remove the library before reinstalling it" functionality); and of course keep the .dek extension.
gfasmf IOhannes