Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Directory permissions and ownership -- RFC
Date: Tue, 21 Jun 2011 19:35:29 -0500	[thread overview]
Message-ID: <4E0138D1.409@windriver.com> (raw)
In-Reply-To: <1308692250.3083.79.camel@lenovo.internal.reciva.com>

On 6/21/11 4:37 PM, Phil Blundell wrote:
> On Tue, 2011-06-21 at 16:27 -0500, Mark Hatle wrote:
>> I don't know how to do this within bitbake (easily).  The table is currently a
>> static set of paths that exist within the distribution as a whole.  They are not
>> recipe specific, but you can have more then one file... the assumption is
>> different layers may bring in additional files, only if necessary.
>>
>> If there is existing code I can use to identify and resolve in-line variables,
>> I'll be happy to add that into the code.  I'd certainly like to add that
>> capability, but so far we don't have it.  (Would be nice in the device_table
>> file.. but I doubt that's practical as the code is not run within python.)
> 
> I think bb.data.expand() should do what you need there.
> 
> p.
> 
> 

Based on the above, I reworked the package.bbclass commit.  The new version is
located at:

http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=mhatle/perms&id=7b59d7817771ba6bcf85a9816910e2bc036acf52

Functionally it's almost the same, but structurally it has changed a lot.  From
the last version to this version:

* create a local (to fixup_perms) a function to actually setup the data structure

* remove the default documentation, locale and header correction entries
  - move them to the fs-perms.txt

* When processing a "line" to setup the data structure, we expand all of the
variables with it first.  This not only allows for the directory to be set with
a variable, but also the mode, uid, and gid if necessary.

--Mark



  reply	other threads:[~2011-06-22  0:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 16:43 Directory permissions and ownership -- RFC Mark Hatle
2011-06-21 18:57 ` Phil Blundell
2011-06-21 19:12   ` Mark Hatle
2011-06-21 21:09     ` Phil Blundell
2011-06-21 21:27       ` Mark Hatle
2011-06-21 21:37         ` Phil Blundell
2011-06-22  0:35           ` Mark Hatle [this message]
2011-06-22  5:47         ` Anders Darander
2011-06-21 21:32     ` Koen Kooi
2011-06-21 21:41       ` Mark Hatle
2011-06-21 21:52         ` Phil Blundell
2011-06-21 21:58           ` Phil Blundell
2011-06-21 22:05     ` Richard Purdie
2011-06-21 22:13       ` Mark Hatle
2011-06-22  4:51         ` Mark Hatle
2011-06-22 14:04           ` Mark Hatle

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=4E0138D1.409@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.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