From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/4] acct-group.eclass: Fix for when building in a rooted prefix (EROOT)
Date: Wed, 7 Dec 2022 11:52:58 -0500 [thread overview]
Message-ID: <CAJ0EP40w2MUnd7covLQuTdMdmFCqujiBhy8GedhdbpCkWhryrQ@mail.gmail.com> (raw)
In-Reply-To: <e39520806d6d7917ff03c06680117a7c2ddd77bd.camel@gentoo.org>
On Wed, Dec 7, 2022 at 4:24 AM James Le Cuirot <chewi@gentoo.org> wrote:
> The new eclasses also skip the operation if you are root. As that bug report
> says, running a prefixed system as root is probably unsupported. I was doing
> this as root into a ROOTed prefix though, which is slightly different. Should
> we also skip the operation if EPREFIX non-empty? I'll think about it.
I would be in favor of skipping adding users/groups if EPREFIX is
non-empty, at least as a temporary solution.
If someone presents a use case where adding users to
${EROOT}/etc/passwd makes sense, we can revisit it then.
next prev parent reply other threads:[~2022-12-07 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 22:24 [gentoo-dev] [PATCH 1/4] acct-group.eclass: Fix for when building in a rooted prefix (EROOT) James Le Cuirot
2022-12-06 22:24 ` [gentoo-dev] [PATCH 2/4] acct-user.eclass: " James Le Cuirot
2022-12-06 22:24 ` [gentoo-dev] [PATCH 3/4] user-info.eclass: " James Le Cuirot
2022-12-06 23:57 ` Mike Gilbert
2022-12-06 22:24 ` [gentoo-dev] [PATCH 4/4] user.eclass: " James Le Cuirot
2022-12-06 23:55 ` Mike Gilbert
2022-12-06 23:54 ` [gentoo-dev] [PATCH 1/4] acct-group.eclass: " Mike Gilbert
2022-12-07 9:24 ` James Le Cuirot
2022-12-07 16:52 ` Mike Gilbert [this message]
2022-12-07 17:19 ` Fabian Groffen
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=CAJ0EP40w2MUnd7covLQuTdMdmFCqujiBhy8GedhdbpCkWhryrQ@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@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