|

楼主 |
发表于 2004-3-5 06:58:57
|
显示全部楼层
On Fri, Aug 23, 2002 at 01:38:00AM -0500, Jack Brown wrote:
> I'm just wondering,
>
> why are we instaling procinfo as part of the book? Is there any reason
> we would need this package as part of a base linux system. personally I
> don't think I've ever had any reason to use any of the commands it
> installs and off hand I dont know of any packages that require it.
>
> I can sort of understand why wwe include psmisc and procps, even though
> they're not needed for recompiling anything or required by any other LFS
> packages (psmisc provides ps, free and top, and procps provides killall
> all of which could be considered base utilities I guess)
>
> For some reason procinfo just seems unnessary... Am I missing something?
I've often wondered the same thing, but not enough to worry about it 
I just put it down to a case of it being a personal preference of
Gerard's. It's his book afterall!
Using your methodology, one could ask, why include autoconf, automake and
libtool? Those packages are not required to install stuff from tarballs.
(before anyone jumps in here and says package XYZ needs blah - well, that
package is broken!). These packages are basically "package building" tools
or put another way, "maintainer" tools. But of course they are generally
needed when building stuff out of CVS.
I can remember when I first started out on Linux and didn't have a clue, I
was horrified when compiling my first package that the autoconf output
read like so:-
checking for working aclocal... no
checking for working autoconf... no
checking for working automake... no
checking for working autoheader... no
I just naturally assumed I needed those pacakages and went and installed
them. Little did I know..
Greg
--
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message |
|