From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot "install" wrapper to preserve file permissions
Date: Tue, 05 Apr 2011 21:58:46 +0200 [thread overview]
Message-ID: <87ipuswjux.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110405215447.135159ef@surf> (Thomas Petazzoni's message of "Tue, 5 Apr 2011 21:54:47 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> How would you like this sort of approach in Buildroot?
Thomas> Yesterday, I've implemented something that allows each package to add
Thomas> contents to the device table, so that packages can create additional
Thomas> device files, or adjust the permissions of the files they install. I
Thomas> needed this to fix the dbus package, which requires a particular
Thomas> program to have strict permission and ownership properties.
Thomas> Basically, each package can do:
Thomas> define <pkg>_PERMISSION_TABLE
Thomas> some content exactly similar to a device table fragment
Thomas> endef
Thomas> and it will automatically be appended to the device table if the
Thomas> package is enabled.
Thomas> Would that match your needs ?
I think Daniel's proposal is to use a custom install program (wrapper),
which would then automatically create those device_table.txt snippets.
I like the idea.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-04-05 19:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 7:48 [Buildroot] Buildroot "install" wrapper to preserve file permissions Daniel Nyström
2011-04-05 19:54 ` Thomas Petazzoni
2011-04-05 19:58 ` Peter Korsgaard [this message]
2011-04-05 20:32 ` Daniel Nyström
2011-04-05 21:42 ` Thomas Petazzoni
2011-04-05 22:00 ` Daniel Nyström
2011-04-06 6:59 ` Peter Korsgaard
2011-04-06 7:32 ` Daniel Nyström
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=87ipuswjux.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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