public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Longland <stuartl@longlandclan.hopto.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] sys-apps is too big
Date: Wed, 02 Mar 2005 09:21:05 +1000	[thread overview]
Message-ID: <4224F8E1.8030407@longlandclan.hopto.org> (raw)
In-Reply-To: <20050301153738.23dfd833@snowdrop>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Ciaran McCreesh wrote:
> On Tue, 01 Mar 2005 20:40:01 +1000 Stuart Longland
> <stuartl@longlandclan.hopto.org> wrote:
> | Well... technically it is an editor... the name comes from Stream
> | EDitor -- and it does indeed do exactly that -- you pass some text
> | into stdin, give it some rules... and edited text comes out stdout.
>
> So? Both are primarily used as core system utilities, not as editors, so
> they stay in sys-apps.
>

Yes... but in the "core utility role" what does sed and ed do?  Edit
files & streams.  They are scripted editors -- and should be recognised
as such.

--
+-------------------------------------------------------------+
| Stuart Longland -oOo- http://stuartl.longlandclan.hopto.org |
| Atomic Linux Project     -oOo-    http://atomicl.berlios.de |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| I haven't lost my mind - it's backed up on a tape somewhere |
+-------------------------------------------------------------+

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-03-01 23:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 19:00 [gentoo-dev] sys-apps is too big Ciaran McCreesh
2005-02-23 19:07 ` Henrik Brix Andersen
2005-02-23 19:23 ` Martin Schlemmer
2005-02-23 19:35   ` Mike Frysinger
2005-02-23 22:31   ` tchiwam
2005-02-23 22:51     ` Jim Northrup
2005-02-23 22:55       ` Mike Frysinger
2005-02-23 22:51     ` Greg KH
2005-02-23 21:43 ` Olivier Crête
2005-02-27 20:23 ` Ciaran McCreesh
2005-02-27 22:09   ` Martin Schlemmer
2005-03-01  1:21   ` Robin H. Johnson
2005-03-01  1:34     ` Olivier Crête
2005-03-01  1:41       ` [gentoo-dev] x86 vs amd64 :: ppc vs ppc64 (was sys-apps is too big) Mike Frysinger
2005-03-01  1:49         ` Stephen P. Becker
2005-03-01  2:00           ` Mike Frysinger
2005-03-04  2:32         ` Kumba
2005-03-04  2:50           ` Mike Frysinger
2005-03-01  8:20     ` [gentoo-dev] sys-apps is too big Ciaran McCreesh
2005-03-01  9:50       ` Martin Schlemmer
2005-03-01 10:40       ` Stuart Longland
2005-03-01 11:54         ` Georgi Georgiev
2005-03-01 12:11           ` Stuart Longland
2005-03-01 14:08         ` [gentoo-dev] " Thomas Kirchner
2005-03-01 14:37           ` Robin H. Johnson
2005-03-01 14:55             ` [gentoo-dev] " Thomas Kirchner
2005-03-01 15:37         ` [gentoo-dev] " Ciaran McCreesh
2005-03-01 23:21           ` Stuart Longland [this message]
2005-03-01 23:33             ` Ciaran McCreesh
2005-03-01 23:40               ` Robin H. Johnson
2005-03-01 23:46                 ` Mike Frysinger
2005-03-01 23:48                 ` Ciaran McCreesh
2005-03-01 11:12     ` Aaron Walker
2005-03-01 18:08   ` Ciaran McCreesh
2005-03-03 20:43     ` Ciaran McCreesh

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=4224F8E1.8030407@longlandclan.hopto.org \
    --to=stuartl@longlandclan.hopto.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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