From: Peter Johanson <latexer@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Additions to /etc/{group,passwd,shadow}
Date: Mon, 21 Jul 2003 21:09:48 -0400 [thread overview]
Message-ID: <20030722010947.GB6073@gonzo.peterjohanson.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
hey all,
got working on an ebuild that required to have a new user and group
added, and had to break down to asking in #gentoo-dev the process, and
then having seemant say, i paraphrase, "yeah, something like that."
Problem seems to be a lack of policy/documentation on the process
involved. It seems quite a few entries in /etc/{group,passwd} are just
coded into baselayout, but i could be wrong on this. Currently, the
approach taken in most ebuilds is to add users/groups in the pkg_setup()
phase of an ebuild.
http://bugs.gentoo.org/show_bug.cgi?id=8634
This bug contains a discussion of a new approach that seems to be the
way we're going with this stuff. This involves the eid_database and
enew{user,group} stuff discussed previously. seemant asked that i bring
this stuff up so we can get the ball really rolling on getting things
finally implemented and then establishing policy and documentation for
this stuff.
comments, concerns, ideas, etc?
-pete "just-wanted-to-add-a-user-and-a-group-for-one-ebuild" johanson
--
Peter Johanson
<latexer@gentoo.org>
Key ID = 0x6EFA3917
Key fingerprint = A90A 2518 57B1 9D20 9B71 A2FF 8649 439B 6EFA 3917
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-07-22 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 1:09 Peter Johanson [this message]
2003-07-22 1:58 ` [gentoo-dev] Additions to /etc/{group,passwd,shadow} Mike Frysinger
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=20030722010947.GB6073@gonzo.peterjohanson.com \
--to=latexer@gentoo.org \
--cc=gentoo-dev@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