From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Why chmod ug+rw?
Date: Wed, 6 Jul 2011 19:00:37 +0200 [thread overview]
Message-ID: <201107061900.37544.arnout@mind.be> (raw)
Hoi all,
Why does buildroot make the sources group-writable?
A bit of context: I'm using Thomas Petazzoni's patch to have a custom package
extract function that rsyncs the source code into the build directory. I
noticed that rsync always goes through the whole tree, because it needs to
update permissions. This is because of the below:
$($(PKG)_EXTRACT_CMDS)
# some packages have messed up permissions inside
$(Q)chmod -R ug+rw $(@D)
Now I agree that some packages have messed up permissions, but why does the
group need read and write permission? Especially since in buildroot
everything is owned by the user and no su-ing is done.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next reply other threads:[~2011-07-06 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 17:00 Arnout Vandecappelle [this message]
2011-07-07 8:14 ` [Buildroot] Why chmod ug+rw? Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201107061900.37544.arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox