From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [rfc] drop iputils from @system (i.e. ping)
Date: Thu, 15 Oct 2015 06:57:29 -0400 [thread overview]
Message-ID: <CAGfcS_=n3SZrCUVmnXVQueE0NVm776uwj8xK4oLOUfshbzD_Vg@mail.gmail.com> (raw)
In-Reply-To: <20151015033955.GJ4446@vapier.lan>
On Wed, Oct 14, 2015 at 11:39 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> iputils is currently in @system for everyone. by default, it only
> installs `ping`. do we feel strongly enough about this to require
> all systems include it ? or should this wait for the long idea of
> releasing stage4's instead of stage3's ?
IMO this should certainly be installed by default, but it should also
not be a part of the @system set unless portage depends on it or
something like that.
Thus this should probably wait until we start releasing stage4s.
The fact that everybody wants a package to be installed shouldn't be a
reason to put it in the @system set. It should instead be a reason to
have some tool other than the @system set to give everybody what they
want. We need one set for the stuff that everybody agrees is
indispensable (@tbd), and a different set for the minimum set of
software (@system) you need to bootstrap the rest of the packages in
the repo.
--
Rich
next prev parent reply other threads:[~2015-10-15 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 3:39 [gentoo-dev] [rfc] drop iputils from @system (i.e. ping) Mike Frysinger
2015-10-15 3:57 ` Andrew Udvare
2015-10-15 9:06 ` Dale
2015-10-15 8:08 ` Tobias Klausmann
2015-10-15 8:13 ` Alexis Ballier
2015-10-15 11:34 ` Anthony G. Basile
2015-10-15 11:33 ` Anthony G. Basile
2015-10-15 8:26 ` [gentoo-dev] " Duncan
2015-10-15 10:57 ` Rich Freeman [this message]
2015-10-15 14:58 ` [gentoo-dev] " Ian Stakenvicius
2015-10-15 11:24 ` Anthony G. Basile
2015-10-15 13:26 ` Michael Orlitzky
2015-10-15 14:00 ` hasufell
2015-10-15 15:13 ` 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='CAGfcS_=n3SZrCUVmnXVQueE0NVm776uwj8xK4oLOUfshbzD_Vg@mail.gmail.com' \
--to=rich0@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