From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] fs/common.mk: Add support for fakeroot script
Date: Sun, 27 Oct 2013 10:30:53 +0100 [thread overview]
Message-ID: <526CDD4D.70307@mind.be> (raw)
In-Reply-To: <20131015132102.GA20116@gmail.com>
On 15/10/13 15:21, Andrew Ruder wrote:
> This adds a BR2_ROOTFS_FAKE_ROOT_SCRIPT (similar to
> BR2_ROOTFS_POST_BUILD_SCRIPT and BR2_ROOTFS_POST_IMAGE_SCRIPT). This
> script is called inside the fakeroot which allows the script to change
> permissions, create device nodes, etc.
>
> Signed-off-by: Andrew Ruder <andrew.ruder@elecsyscorp.com>
> ---
> I am using this script as part of a configuration that creates a bunch
> of directories that need to have specific ownership. I can create
> the directories in a post-build script, but permissions needed to be
> done in a fakeroot environment. Didn't see any other way to hook into
> the fakeroot.
Hi Andrew,
At the buildroot developer meeting we decided to drop this patch. For
your particular use case, there is a better way to do it with
<pkg>_PERMISSIONS or with the device table. We also discussed other use
cases, like doing an rsync inside the fakeroot, but these use cases can
just untar the tarball in a post-image script and work on that. And
finally, having all these different POST_xxx steps makes things confusing.
If you still see a reason to add this feature, don't hesitate to tell us.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-10-27 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 13:21 [Buildroot] [RFC PATCH] fs/common.mk: Add support for fakeroot script Andrew Ruder
2013-10-15 14:19 ` Thomas Petazzoni
2013-10-18 20:23 ` Andrew Ruder
2013-10-18 20:49 ` Yann E. MORIN
2013-10-18 21:35 ` Andrew Ruder
2013-10-18 22:07 ` Yann E. MORIN
2013-10-27 9:30 ` Arnout Vandecappelle [this message]
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=526CDD4D.70307@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