* DG Ward <david.w...@zerospace.co.nz> [131122 07:03]: > Hey guys, > > I've been working away on fixing the problem described here: > http://bugs.call-cc.org/ticket/942 > > The problem only manifests itself when you install via. sudo. > > The reason that the issue arose is that no owner was specified for > the files being installed. This meant that the owner defaulted to > the person who ran the command. > > That itself may not seem like it should screw up the permissions as > they were directly specified (e.g. -m755). The gotcha? Sudo doesn't > let issued programs set a umask that's more permissive than that of > the invoking user. > > Explicitly stating the owner as root lets us set the mode to > whatever we please :)
Changing the userid to "root" is not a good solution: It works except for local installs, where this trick breaks the install: $ make PLATFORM=linux PREFIX=~/chickentest install [...] install -d -o root -g root "/home/ckeen/chickentest/lib" install: cannot change owner and permissions of '/home/ckellerm/ckeen/lib': Operation not permitted [...] I don't know if that really is a global problem at all. I have never noticed this on my systems. Which OS are you running? Would it be possible for you to set the -g option in your sudo config? Kind regards, Christian -- In the world, there is nothing more submissive and weak than water. Yet for attacking that which is hard and strong, nothing can surpass it. --- Lao Tzu _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-hackers
