From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] useradd.bbclass: fix how RDEPENDS is setup
Date: Sun, 06 Nov 2011 15:07:45 -0800 [thread overview]
Message-ID: <4EB71341.3020602@intel.com> (raw)
In-Reply-To: <1320611116.3041.2.camel@lenovo.internal.reciva.com>
On 11/06/2011 12:25 PM, Phil Blundell wrote:
> On Sun, 2011-11-06 at 11:31 -0800, Scott Garman wrote:
>> Fix bug where only packages named PN included base-passwd in
>> RDEPENDS. Also remove shadow requirement, since some targets
>> do not use shadow and file ownership can be changed with only
>> passwd/group entries.
>>
>> This fixes [YOCTO #1727]
>
> Don't you need shadow or some equivalent to provide /sbin/useradd so
> that the postinsts work for on-target installs? Removing shadow from
> RDEPENDS does sound like a good plan for the no-package-management case,
> but I'm not sure it's safe otherwise.
Of course you're right. Thank you for pointing this out. I will spin a
v2 of the patchset.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-11-06 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 19:31 [PATCH 0/1] useradd.bbclass: fix how RDEPENDS is setup Scott Garman
2011-11-06 19:31 ` [PATCH 1/1] " Scott Garman
2011-11-06 20:25 ` Phil Blundell
2011-11-06 23:07 ` Scott Garman [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-11-06 23:27 [PATCH 0/1] useradd.bbclass: fix how RDEPENDS is setup [v2] Scott Garman
2011-11-06 23:27 ` [PATCH 1/1] useradd.bbclass: fix how RDEPENDS is setup Scott Garman
2011-11-07 23:36 [PATCH 0/1] useradd.bbclass: fix how RDEPENDS is setup [v3] Scott Garman
2011-11-07 23:36 ` [PATCH 1/1] useradd.bbclass: fix how RDEPENDS is setup Scott Garman
2011-11-08 14:09 ` Richard Purdie
2011-11-08 16:24 ` Scott Garman
2011-11-08 16:58 ` Richard Purdie
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=4EB71341.3020602@intel.com \
--to=scott.a.garman@intel.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