From: Daniel Pielmeier <daniel.pielmeier@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Managing users and groups
Date: Sun, 09 Sep 2007 06:14:27 +0200 [thread overview]
Message-ID: <46E37323.8000302@googlemail.com> (raw)
In-Reply-To: <200709082339.19171.vapier@gentoo.org>
Mike Frysinger schrieb:
> On Saturday 08 September 2007, Daniel Pielmeier wrote:
>> While writing this i have found GLEP-27. What is the current status
>> concerning this?
>
> presumably you'd search bugzilla and come across 53269
> -mike
I have searched bugzilla, but not for the specific glep. This does not
look like a big issue as there is no progress in this bug at all (sorry
i can not help out there, i am just a user not a programmer as i have
mentioned before).
Why not using something similar to Comment 16 in Bug 8634
USERDEPEND="someuser"
GROUPDEPEND="somegroup"
A group/user is created when no other ebuild has the dependency and is
removed when the last ebuild has been removed which needs it?
Okay the approach in the glep look much cleaner, but this is maybe more
easier to implement!
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-09-09 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 2:47 [gentoo-dev] Managing users and groups Daniel Pielmeier
2007-09-09 3:39 ` Mike Frysinger
2007-09-09 4:14 ` Daniel Pielmeier [this message]
2007-09-09 8:15 ` Philipp Riegger
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=46E37323.8000302@googlemail.com \
--to=daniel.pielmeier@googlemail.com \
--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