| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
This seems to be opposite of my reply I just sent :) |
| 5 |
I would agree that man-pages (and maybe man also, but many packages depend on |
| 6 |
it without mentioning it in DEPEND) should probably not be in system (along |
| 7 |
with all other documents). In fact, it would probably be a good idea to make |
| 8 |
a 'man' and 'info' USE flag and only install manpages/infopages when they are |
| 9 |
set. |
| 10 |
Some users may *require* the ability to change console font or keyboard layout |
| 11 |
to use the system (for example, if their system is weird and has a messed up |
| 12 |
default font or something, or if someone has a physically QWERTY keyboard, |
| 13 |
but uses Dvorak) |
| 14 |
ext2/ext3 are still considered Linux native, so that may be justification for |
| 15 |
their inclusion in system, if not for the fact that reiserfs is a bad idea |
| 16 |
for a /boot partition... I wouldn't have any objection to their removal from |
| 17 |
system, though. |
| 18 |
If rsync is in system, it probably should be removed. Portage could quite |
| 19 |
easilly just install it when the user tries to sync if need be. |
| 20 |
hdparm, fbset may also be neccesary for system usage in some cases. I would |
| 21 |
agree that 'less' does not belong in system, though. |
| 22 |
To exclude network related programs from system, one would have to modify |
| 23 |
baselayout to use the nonetwork initlevel by default logically, and I don't |
| 24 |
think that would be too simple (and might require a 'network' USE flag). |
| 25 |
|
| 26 |
|
| 27 |
On Saturday 23 August 2003 08:34 pm, Yuri Enshin wrote: |
| 28 |
> Hmm... May be, extend your question? |
| 29 |
> Some users know all about linux, so no reason to include man and |
| 30 |
> man-pages in system. |
| 31 |
> Some users never change default console font or keyboard layout, so no |
| 32 |
> reason to include kbd or console-tools in system. |
| 33 |
> Some users have no ext2/ext3 partiotions, so no reason to include in |
| 34 |
> system e2fsprogs. |
| 35 |
> Some users never use 'emerge sync' (only download snapshots), so no |
| 36 |
> reason to include rsync. |
| 37 |
> Some users never use less, hdparm, fbset... |
| 38 |
> Some users have no network on computer at all, so no reason to include |
| 39 |
> any network related programs in system. |
| 40 |
> I can continue this list. |
| 41 |
> |
| 42 |
> The reason for dhcpcd *in* system, IMHO: support for dhcp client - part |
| 43 |
> of universal, standart set of full-functional network-ready computer. |
| 44 |
> |
| 45 |
> |
| 46 |
> |
| 47 |
> -- |
| 48 |
> gentoo-dev@g.o mailing list |
| 49 |
|
| 50 |
- -- |
| 51 |
Luke-Jr |
| 52 |
Developer, Gentoo Linux |
| 53 |
http://www.gentoo.org/ |
| 54 |
-----BEGIN PGP SIGNATURE----- |
| 55 |
Version: GnuPG v1.2.2 (GNU/Linux) |
| 56 |
|
| 57 |
iD8DBQE/R/W0Zl/BHdU+lYMRAvAHAJ93CIljUzyPAs2Mrk3XcOhcfqcX6gCgj/Be |
| 58 |
AwTJs10N232qrdxS4XmPSUQ= |
| 59 |
=VCT1 |
| 60 |
-----END PGP SIGNATURE----- |
| 61 |
|
| 62 |
|
| 63 |
-- |
| 64 |
gentoo-dev@g.o mailing list |
Archives