Marco S Hyman wrote:
Maurice Janssen writes:
> >Is there anyway to _not_ get these extra sets as part of
> >following stable? I don't know that it hurts anything, but I have no
> >use for them on the system and would like to keep it as minimalistic as
> >possible.
>
> I'm sure it's possible to modify the tree in some way to prevent this,
> but that's not supported and it may break other things (like cvs
> updates).
If you want to go unsupported and non-standard you can play with the
makefiles. Games is easy: remove "games" from the list of SUBDIR in
/usr/src/Makefile. misc is quite a bit harder as it contains
the documentation for thing that you still want built and installed.
> I guess the easiest way is to build a release on another system and
> install only the file sets that you used during the initial
> installation.
Or, let it install then remove the unneeded files. The source contains
a list of everything in a set and in the case of misc everything is
machine independat. After a build you could do something like this
(untested):
cd /
# remove the regular files
cat /usr/src/distrib/sets/lists/misc/mi |
while read f; do test -f $f && rm $f; done
# remove the directories
tail -r /usr/src/distrib/sets/lists/misc/mi |
while read d; do test -d $d && rmdir $d; done
// marc
Ok this has answered the question, and thanks. This raises another
question for me.. If updating just the sets that you install, and I am
making an assumption here that people would want to update code when
needed, and be supported, why even give the choice on which sets to
install initially if the two extra sets will be installed anyway during
the supported method of updating?
Thanks again,
Aaron
