From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] enewuser/enewgroup getting their own eclass
Date: Wed, 23 Nov 2005 12:38:44 -0800 [thread overview]
Message-ID: <4384D354.9020206@gentoo.org> (raw)
In-Reply-To: <1132775642.27288.159.camel@cgianelloni.nuvox.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Gianelloni wrote:
| That is what I thought. I was just wondering if there were some other
| *DEPEND that I wasn't aware of that fit the bill of "needed for
| installing from a package but not needed afterwards". It doesn't
| *really* matter since shadow is in "system" on any machine this would
| affect anyway, but you get my thinking.
/me begins clamoring for IDEPEND (install-time deps).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDhNNUXVaO67S1rtsRAodMAJ0ZxD7gWiRU7r1SggpH/Bgd7NZ4mACg2N8Y
onOzQzXwd/6hrO7+acpLonQ=
=qGhH
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-23 20:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 18:15 [gentoo-dev] enewuser/enewgroup getting their own eclass Chris Gianelloni
2005-11-23 18:30 ` Diego 'Flameeyes' Pettenò
2005-11-23 19:22 ` Chris Gianelloni
2005-11-23 20:06 ` [gentoo-dev] " Duncan
2005-11-23 20:21 ` Robin H. Johnson
2005-11-23 20:29 ` Chris Gianelloni
2005-11-23 21:14 ` [gentoo-dev] " Duncan
2005-11-23 21:28 ` Ciaran McCreesh
2005-11-23 21:29 ` Ned Ludd
2005-11-23 22:02 ` Jakub Moc
2005-11-23 18:52 ` [gentoo-dev] " Brian Harring
2005-11-23 19:31 ` Chris Gianelloni
2005-11-23 19:40 ` Donnie Berkholz
2005-11-23 19:54 ` Chris Gianelloni
2005-11-23 20:38 ` Donnie Berkholz [this message]
2005-11-23 22:54 ` Henrik Brix Andersen
2005-11-23 21:03 ` Donnie Berkholz
2005-11-23 23:17 ` Henrik Brix Andersen
2005-11-24 3:44 ` Mike Frysinger
2005-11-24 13:54 ` Chris Gianelloni
2005-11-24 19:34 ` Mike Frysinger
2005-11-25 14:24 ` Chris Gianelloni
2005-11-25 19:24 ` Mike Frysinger
2005-11-30 14:51 ` Chris Gianelloni
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=4384D354.9020206@gentoo.org \
--to=spyderous@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