From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] cleaning out 'bc' and 'ed' from system
Date: Fri, 22 Apr 2005 08:59:40 -0400 [thread overview]
Message-ID: <1114174780.889.10.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20050422064651.GA7439@sympatico.ca>
[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]
On Fri, 2005-04-22 at 02:46 -0400, Philip Webb wrote:
> 050421 Juha Varkki wrote:
> > 050421 Mike Frysinger wrote:
> >> we've had 'bc' and 'ed' around for historical reasons
> >> and because we've never actually tracked what packages invoke them
> > Do you mean /usr/bin/bc or did I miss something?
> > Why on earth are you taking it out? I use bc quite often actually ..
>
> surely the idea of 'system' is to provide all those basic tools
> which someone might need when doing sysadmin things without X .
> that's why Lynx is included, to allow seeking WWW help & downloading things.
> Ed is there because it's needed for Sed, which is useful for sysadmin;
> Bc has a similar usefulness. all at basic console level.
Ehh... lynx isn't in system.
As for Gentoo's definition of "system" it is everything you *require* to
have a functioning Linux system at the shell, not everything you might
*want* to have. It is supposed to be as minimal as possible, and it is
up to you to build on it to get the system the way you want.
I say dump them from system. Two less things that I have to have in
every stage3 tarball and on every release CD.
> as they say, if it ain't broke, don't fix it:
> try to understand why it was done that way originally.
It *is* broken if it is wasting space on the release media.
The truth is that we remove them during the creation of the release CD,
since we don't use them. However, they are still in the stages, and on
x86, where we have 5 stage3 images, that is 5 times the wasted space on
the Universal InstallCD and 10 times the wasted space on the mirrors!
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-22 12:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 17:06 [gentoo-dev] cleaning out 'bc' and 'ed' from system Mike Frysinger
2005-04-21 17:17 ` Ciaran McCreesh
2005-04-21 19:09 ` Juha Varkki
2005-04-21 19:19 ` Maurice van der Pot
2005-04-21 20:29 ` Mike Frysinger
2005-04-21 21:30 ` Luis F. Araujo
2005-04-21 22:18 ` Donnie Berkholz
2005-04-21 23:21 ` Luis F. Araujo
2005-04-21 23:26 ` Alec Joseph Warner
2005-04-22 1:15 ` Chris Gianelloni
2005-04-22 6:46 ` Philip Webb
2005-04-22 7:09 ` Alin Nastac
2005-04-22 14:05 ` Spider
2005-04-22 17:16 ` Alin Nastac
2005-04-22 23:35 ` Luke Ravitch
2005-04-22 23:58 ` Mike Frysinger
2005-04-24 18:45 ` Anthony de Boer
2005-04-24 19:15 ` Alec Warner
2005-04-24 20:27 ` Jan Kundrát
2005-04-24 20:54 ` Athul Acharya
2005-04-24 21:04 ` Mike Frysinger
2005-04-22 12:59 ` Chris Gianelloni [this message]
2005-04-22 13:06 ` Alec Joseph Warner
2005-04-21 17:17 ` Robin H. Johnson
2005-04-22 21:29 ` Drake Wyrm
2005-04-22 21:38 ` Ciaran McCreesh
2005-04-22 21:49 ` David Klaftenegger
2005-04-22 21:54 ` Mike Frysinger
2005-04-22 21:58 ` David Klaftenegger
2005-04-23 3:32 ` Drake Wyrm
2005-04-23 3:41 ` Georgi Georgiev
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=1114174780.889.10.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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