From: Andreas Oberritter <obi@opendreambox.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] package_ipk: apply umask to control and conffiles
Date: Fri, 23 Mar 2012 21:17:38 +0100 [thread overview]
Message-ID: <4F6CDA62.3070908@opendreambox.org> (raw)
In-Reply-To: <1331567634.15192.20.camel@ted>
On 12.03.2012 16:53, Richard Purdie wrote:
> On Mon, 2012-03-12 at 10:29 -0500, Mark Hatle wrote:
>> On 3/9/12 8:15 PM, Andreas Oberritter wrote:
>>> * Explicitly set umask to 022. Otherwise the build system's
>>> umask leaks into the image.
>>
>> I'm surprised that do_package_ipk[umask] didn't work. Perhaps its the way it's
>> being invoked that is the issue. (If bitbake doesn't run it, but something else
>> does.. then the umask setting doesn't get used.)
>>
>> As for the change of the umask, the changes appear to be specific to the ipk
>> case. Is this the desired behavior, or could deb and rpm suffer from similar
>> issues? (I'm not familiar enough with opkg to know how it handles umask
>> settings during package install/rootfs construction..)
>>
>> I believe that RPM sets a default umask when it goes through it's package
>> installs/rootfs generation. But does DEB?
>
> I'm also a bit worried about this patch. I'd like to understand why a
> task level umask doesn't work. That shouldn't even make any difference
> since the permissions/owners/users from install should be getting
> used...
>
> Cheers,
>
> Richard
Richard,
can you please give some advise on how to continue with this issue?
Regards,
Andreas
next prev parent reply other threads:[~2012-03-23 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 2:15 [PATCH] package_ipk: apply umask to control and conffiles Andreas Oberritter
2012-03-12 15:29 ` Mark Hatle
2012-03-12 15:53 ` Richard Purdie
2012-03-12 16:27 ` Andreas Oberritter
2012-03-23 20:17 ` Andreas Oberritter [this message]
2012-03-26 11:34 ` Richard Purdie
2012-03-26 15:47 ` Andreas Oberritter
2012-04-04 16:56 ` Saul Wold
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=4F6CDA62.3070908@opendreambox.org \
--to=obi@opendreambox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.