Hi IOhannes
Thanks for your comments!
On Sun, 2024-06-02 at 23:15 +0200, IOhannes m zmölnig wrote:
the filename problem is not limited to ecryptfs (actually, it shouldn't be a problem with ecryptfs, at least for consumers: when deken downloads a package, it excludes the architectures in the local file; however, the files must be storable on the machines that create the deken package (hopefully using a less limited filesystem and on the servers)
Ah, good to know. Actually, I triggered the filename length limit while creating a package containing 4 Linux archs with each having both floatsizes with Deken. Then I remembered that I ran into this problem years ago while downloading a package, which is apparently not a problem anymore.
the assumption is, that people who like to switch between floatsizes (Pd32/Pd64) and CPU architectures without wanting to re-install the package, will typically use the same OS (that is: few people have the same filesystem mounted under at least two of Linux, macOS & Windows)
Sounds reasonable.
Roman