From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Directory permissions and ownership -- RFC
Date: Tue, 21 Jun 2011 16:41:08 -0500 [thread overview]
Message-ID: <4E010FF4.2070102@windriver.com> (raw)
In-Reply-To: <7E1967A9-8BDC-4B6D-85FB-0232590DD15A@dominion.thruhere.net>
On 6/21/11 4:32 PM, Koen Kooi wrote:
>
> Op 21 jun 2011, om 21:12 heeft Mark Hatle het volgende geschreven:
>
>> On 6/21/11 1:57 PM, Phil Blundell wrote:
>>> On Tue, 2011-06-21 at 11:43 -0500, Mark Hatle wrote:
>>>> Adjust the umask to 022. This resolves the problem of dynamically generated
>>>> directories (mkdir -p) and specific files (touch foo) having odd permissions.
>>>>
>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=mhatle/perms&id=d8470b6a8efdbba04cef5d4dc1ce12720fe83621
>>>
>>> Are you confident that this isn't going to break anything like
>>> group-shared DL_DIRs? I'm not entirely thrilled about forcing the umask
>>> to 022 for everything that bitbake does, although I can see that making
>>> it be so for particular tasks like do_install() might have some merit.
>>> Even in the latter case, though, I wonder whether we should just be
>>> paying more attention to recipe hygiene and using "install -m ..." with
>>> the permissions that we actually want.
>>
>> This is why I bring this up.. I'm a bit concerned that doing it generally will
>> have unintended consequences. So far I am not aware of any. Moving it to a
>> different place in the process may be better. The only issue I've found so far
>> is that just coding int into "do_install" really isn't an option. Between the
>> custom do_install components, various classes, etc.. it's difficult in the
>> current infrastructure to find a centralized location to set the value.
>
> Would something like this work?
>
> myclass.bbclass:
>
> addtask mytask before do_package after do_install
>
> mytask() {
> do stuff
> }
Unfortunately it won't work as the umask would only be set in the "mytask" -
task. It needs to be set in all of the do_install and do_package tasks.
The only way to do this (from what Chris L told me) is to setup an event handler
and set the umask when we get into specific events. I'm not sure if I could
correctly capture do_install and later.. plus if someone did what you are
mentioning, then it would no longer be in the umask 022.
> DISTRO.conf:
>
> # do stuff
> INHERIT += "myclass"
>
> regards,
>
> Koen
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-21 21:44 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
2011-06-22 5:47 ` Anders Darander
2011-06-21 21:32 ` Koen Kooi
2011-06-21 21:41 ` Mark Hatle [this message]
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=4E010FF4.2070102@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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