From: Andrew Ruder <andrew.ruder@elecsyscorp.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] fs/common.mk: Add support for fakeroot script
Date: Fri, 18 Oct 2013 15:23:23 -0500 [thread overview]
Message-ID: <20131018202323.GA23065@gmail.com> (raw)
In-Reply-To: <20131015161941.5d7ffd45@skate>
On Tue, Oct 15, 2013 at 04:19:41PM +0200, Thomas Petazzoni wrote:
> Well, the conventional way would be to have those directories created
> by packages (and they can use the <pkg>_PERMISSIONS mechanism to get
> proper ownership or permissions). Or, if they really don't belong to
> any package, create them in the post build script, and have a device
> table assign the permission and ownership.
I didn't realize the device table functionality could modify arbitrary
file/directory ownerships but looking through the makedevs source code
that DOES appear to be true. I guess let's just consider this thread as
a question disguised as a poorly spelled patch. :)
Cheers,
Andy
next prev parent reply other threads:[~2013-10-18 20:23 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 [this message]
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
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=20131018202323.GA23065@gmail.com \
--to=andrew.ruder@elecsyscorp.com \
--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