public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Rebhan <odinshorse@googlemail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: emerge --root : users not created
Date: Mon, 14 Jun 2010 10:09:43 +0200	[thread overview]
Message-ID: <AANLkTilmbTVmCfue38A8eBF4HW4Q7M3q3DM7LqIU0IL9@mail.gmail.com> (raw)
In-Reply-To: <1276268908.1875.29.camel@pr-laptop>

2010/6/11 Marcus Priesch <marcus@priesch.priv.at>:
> Hi sven,
>
> wouldnt it be enough to have the patch included in gentoo's shadow
> ebuild - as i think its mainly relevant for gentoo folks - at least in
> the meantime, until the patch gets accepted upstream ?!

Well, talk to the Gentoo maintainer of the shadow suite. :-) IIRC, it was
clearly said, that the patch has to go through mainstream, but you can
try nevertheless. IMHO the patch really _should_ go upstream and be
reviewed there as it might be relevant for security stuff.

> as i assume this patch alone is not enough - as it needs tweaking the
> eclass providing the eadduser & co functions also ... and therefore it's
> hard to put in an overlay ... or ?!?!

The procedure would be:
1. Get the patch accepted either upstream or in the portage tree.
2. Find a good check to distinguish --chroot enabled and disabled shadow
3. Modify the eclass accordingly.

So, start with 1. and the rest will happen automatically... ;-)

Sven



  reply	other threads:[~2010-06-14  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 10:39 [gentoo-embedded] Re: emerge --root : users not created Marcus Priesch
2010-06-11  8:17 ` Sven Rebhan
2010-06-11 15:08   ` Marcus Priesch
2010-06-14  8:09     ` Sven Rebhan [this message]
2010-06-17 16:57       ` P. Levine
2010-06-17 19:39         ` Ned Ludd
2010-06-17 21:52           ` P. Levine
2010-06-20 11:06   ` P. Levine
2010-06-21  9:24     ` Sven Rebhan
  -- strict thread matches above, loose matches on Subject: below --
2010-02-09  5:48 P. Levine

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=AANLkTilmbTVmCfue38A8eBF4HW4Q7M3q3DM7LqIU0IL9@mail.gmail.com \
    --to=odinshorse@googlemail.com \
    --cc=gentoo-embedded@lists.gentoo.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