Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot "install" wrapper to preserve file permissions
Date: Wed, 06 Apr 2011 08:59:33 +0200	[thread overview]
Message-ID: <87ei5fx3u2.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BANLkTikZ0Dw6ssSc-F9ea2PV2PTxbysj7g@mail.gmail.com> ("Daniel Nyström"'s message of "Wed, 6 Apr 2011 00:00:50 +0200")

>>>>> "Daniel" == Daniel Nystr?m <daniel.nystrom@timeterminal.se> writes:

Hi,

 >> How does this wrapper works ? I'd like to check if it solve my dbus
 >> issue, because I'm not sure that the dbus build system installs it with
 >> the correct ownership (permission will probably be correct, but I'm not
 >> sure about ownership).

 Daniel> There is none yet, but as I think of it, it just adds a line in the
 Daniel> device_table.txt with the path and permission to the installed files.

 Daniel> install -o 1000 -g 1000 -m 755 mybinary /usr/bin/mybinary

Something like that, except it should only do so when called with a
destination directory under $(TARGET_DIR) and only if called with -o or
-g to set owner/group differently than root/root. As a further
complication owner/group can be numeric or names, and names have to get
resolved to the IDs we have in $(TARGET_DIR)/etc/{passwd,group}.

Finally the -o / -g options should get stripped and the request
forwarded to the real install program.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-04-06  6:59 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
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 [this message]
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=87ei5fx3u2.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