public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke-jr@gentoo.org>
To: azarah@gentoo.org
Cc: Yuri Enshin <kot@formoza-centre.ru>, Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] reason for dhcpcd in system profile ?
Date: Mon, 25 Aug 2003 02:18:52 +0000	[thread overview]
Message-ID: <200308250219.08409.luke-jr@gentoo.org> (raw)
In-Reply-To: <1061712914.13460.20.camel@nosferatu.lan>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 24 August 2003 08:15 am, Martin Schlemmer wrote:
> Man pages is an integrate part of a system in my opinion - how anyhow
> are you going to tell them to RTFM if not there :P
Have the install manual suggest installation of them.
>
> > ext2/ext3 are still considered Linux native, so that may be justification
> > for their inclusion in system, if not for the fact that reiserfs is a bad
> > idea for a /boot partition... I wouldn't have any objection to their
> > removal from system, though.
>
> e2fsprogs provide /sbin/fsck ... 8)
fsck, unless I'm mistaken, merely detects the filesystem and runs 
fsck.{ext3,xfs,reiserfs,etc}. It could probably be provided by all packages 
which provide a fsck, or baselayout.
>
> > If rsync is in system, it probably should be removed. Portage could quite
> > easilly just install it when the user tries to sync if need be.
>
> So we devs are going to start moaning because we have rsync installed ?
I doubt anyone is going to whine because they have something they don't need 
installed. The reason to whine is because it's installed *by default*. rsync 
is really cool, but it doesn't really have any reason for being installed 
before the user wants it.
>
> > hdparm, fbset may also be neccesary for system usage in some cases. I
> > would agree that 'less' does not belong in system, though.
>
> Hmm, i would not agree 100% 8)
>
> ------------------------------
> $ PAGER=foo man gcc
> sh: line 1: foo: command not found
> Error executing formatting or display command.
> System command (cd /usr/share/gcc-data/i686-pc-linux-gnu/3.3/man &&
> (echo ".ll 11.1i"; echo ".nr LL 11.1i"; echo ".pl 1100i"; /bin/gunzip -c
> '/usr/share/gcc-data/i686-pc-linux-gnu/3.3/man/man1/gcc.1.gz'; echo;
> echo ".pl \n(nlu+10") | /usr/bin/gtbl | /usr/bin/nroff -Tlatin1 -c
> -mandoc | foo) exited with status 127.
> No manual entry for gcc
> -------------------------------
>
> But then I guess man pages is not needed, right :)  Question is, is
> 'more' needed there - that I would say no, but then I feel 'less' is
> more the default ...
>
> > To exclude network related programs from system, one would have to modify
> > baselayout to use the nonetwork initlevel by default logically, and I
> > don't think that would be too simple (and might require a 'network' USE
> > flag).
>
> In general the 'system' profile have everything that should be needed to
> get a system functioning at a minimal level, with then a few extras that
> we found to be annoying in general.  Take perl - sure its big, but
> automake is a perl script ..... is automake required on a Gentoo box ?
>
> All in all, most things in there is after careful thought - and should
> be removed after 10x more of 'careful thought'.
- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/SXIYZl/BHdU+lYMRAozvAJ93P3oG7v96YyD0Y0eqWsN5AhkxqwCcD3og
Ld3g9krrYTpiwDRrjg2nX5o=
=wdnR
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-25  2:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 19:04 [gentoo-dev] reason for dhcpcd in system profile ? Marius Mauch
2003-08-23 19:20 ` Wolfram Schlich
2003-08-23 20:23   ` Daniel Armyr
2003-08-23 21:20     ` Wolfram Schlich
2003-08-24  6:08       ` Daniel Armyr
2003-08-23 23:06   ` Luke-Jr
2003-08-24  3:21     ` A. Craig West
2003-08-24  8:59       ` Spider
2003-08-24 16:32         ` Alec Berryman
2003-08-24 16:44           ` Spider
2003-08-24 18:16             ` Paul de Vrieze
2003-08-24 18:40               ` Alec Berryman
2003-08-24 18:55               ` Andrew Gaffney
2003-08-24 18:47                 ` Paul de Vrieze
2003-08-24 19:05                   ` Andrew Gaffney
2003-08-24 19:03                     ` Marius Mauch
2003-08-25  0:44                       ` Andrew Gaffney
2003-08-25  0:48                         ` Andrew Gaffney
2003-08-24 22:00         ` Grant Goodyear
2003-08-25  3:07         ` Luke-Jr
2003-08-23 19:29 ` Stewart Honsberger
2003-08-23 20:29   ` Kevyn Shortell
2003-08-24  7:22     ` Stewart Honsberger
2003-08-24  8:33       ` Kevyn Shortell
2003-08-24 15:09         ` Brad Laue
2003-08-24 20:41           ` Kevyn Shortell
2003-08-23 21:25   ` Norberto BENSA
2003-08-23 20:34 ` Yuri Enshin
2003-08-23 21:27   ` Norberto BENSA
2003-08-23 23:16   ` Luke-Jr
2003-08-24  8:15     ` Martin Schlemmer
2003-08-25  2:18       ` Luke-Jr [this message]
2003-08-25  4:24         ` Martin Schlemmer
2003-08-25  4:46         ` Martin Schlemmer
2003-08-25 13:46           ` Luke-Jr
2003-08-25 16:27   ` William Hubbs
2003-08-23 23:08 ` Lloyd D Budd
2003-08-24  4:28   ` Andrew Gaffney
2003-08-24 14:14 ` Marius Mauch
2003-08-24 14:33   ` Martin Schlemmer
2003-08-24 15:09     ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2003-08-24 20:40 Spider

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=200308250219.08409.luke-jr@gentoo.org \
    --to=luke-jr@gentoo.org \
    --cc=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=kot@formoza-centre.ru \
    /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