[Buildroot] Why chmod ug+rw?
Peter Korsgaard
jacmet at uclibc.org
Thu Jul 7 08:14:25 UTC 2011
>>>>> "Arnout" == Arnout Vandecappelle <arnout at mind.be> writes:
Arnout> Hoi all,
Arnout> Why does buildroot make the sources group-writable?
Arnout> A bit of context: I'm using Thomas Petazzoni's patch to have a
Arnout> custom package extract function that rsyncs the source code
Arnout> into the build directory. I noticed that rsync always goes
Arnout> through the whole tree, because it needs to update permissions.
Arnout> This is because of the below:
Arnout> $($(PKG)_EXTRACT_CMDS)
Arnout> # some packages have messed up permissions inside
Arnout> $(Q)chmod -R ug+rw $(@D)
Arnout> Now I agree that some packages have messed up permissions, but
Arnout> why does the group need read and write permission? Especially
Arnout> since in buildroot everything is owned by the user and no
Arnout> su-ing is done.
I don't see any reason for it either. The ug+rw dates back from the
original AUTOTARGETS work (2008, pre-git) by John Voltz who we haven't
heard from for several years:
commit de54a6ebc8f54f01eebd78723003a2f809873030
Author: John Voltz <john.voltz at gmail.com>
Date: Thu Mar 6 18:39:42 2008 +0000
fixed nasty makefile bugs
I'll change it to chmod -R +rw instead.
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list