On 1/8/26 15:21, jyg@gumo.fr wrote:
Hi, What are the guidelines for file and folder permissions in the compressed archives used in deken ?
they should be read/writeable by the user, and at most readable by groups/others.
this is my personal opinion (and not some formally agreed upon "guideline")
files should never be installed as world-writeable, as this is simply a huge security hole.
As a side question : how to force file/folders permission with deken command line utility ?
there's no flag or somesuch (and i don't really see a reason to add one;
see above).
but of course you could just invoke chmod -R after running deken install.
if you are talking about the other way (for creating packages with 'deken') then I also don't see a reason why to allow the user to specify permissions of the file. *however*, 'deken package' should make sure that the permissions are "correct" (that is: readable by the user). in the past I have seen deken archives that had "ugo-rwx" permissions (nobody is allowed to do anything). this is now handled by deken-plugin (when installing), but of course packages should have proper permissions in the first place.
I had trouble installing a package of abstraction (audiolab),
specifically on plugdata (both Windows & OSX), but I also encoutered non-critical errors with puredata on windows 11.> I recreated an .dek archive using Windows compress menu, pulled it on the deken server and this resolved all troubles.
Here is a screenshot that shows the file and folder permissions in
the .dek packages for audiolab(0.7.1) and for the modified version (audiolab_debug).
I'm looking for an explanation why the modified archive resolves the
issue.
the data you have given is very vague. we only now that there is "trouble installing" and "non-critical errors". it's hard to come up with an "explanation" without more information.
if we have a better understanding of your actual problem, my opinion might change (honestly, I doubt it; but I do not understand your problem, so it's hard to tell)
gdasr IOhannes