From: Scott Garman <scott.a.garman@intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] shadow-sysroot: new recipe for useradd.bbclass support
Date: Tue, 21 Jun 2011 15:38:26 -0700 [thread overview]
Message-ID: <4E011D62.4070603@intel.com> (raw)
In-Reply-To: <10377FD6-4D99-467E-9755-A931F6C446E8@dominion.thruhere.net>
On 06/20/2011 11:30 PM, Koen Kooi wrote:
>
> Op 21 jun 2011, om 02:29 heeft Scott Garman het volgende geschreven:
>
>> Packaging login.defs with base-passwd causes problems due to the
>> file being included in target package installs. Instead, this
>> shadow-sysroot recipe can be used by useradd.bbclass to put
>> login.defs into the target sysroot without disturbing packages
>> intended for target devices.
>
> So how does it end up on the target device after this?
login.defs would still end up on the target device when you install the
shadow (target) package. Otherwise the file is not needed (and hence,
should not have been packaged with base-passwd to begin with - my bad).
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-06-21 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 0:29 [PATCH 0/2] login.defs move Scott Garman
2011-06-21 0:29 ` [PATCH 1/2] shadow-sysroot: new recipe for useradd.bbclass support Scott Garman
2011-06-21 6:30 ` Koen Kooi
2011-06-21 22:38 ` Scott Garman [this message]
2011-06-21 0:29 ` [PATCH 2/2] base-passwd: remove login.defs references Scott Garman
2011-06-30 3:57 ` [PATCH 0/2] login.defs move 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=4E011D62.4070603@intel.com \
--to=scott.a.garman@intel.com \
--cc=koen@dominion.thruhere.net \
--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