[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

tagging parts for optional removal.

Been compiling my little heart out on the 2.7 beta stuff.

While it's still in beta, can I offer this:

I've done the changes on my system to start to make it easy
NOT to include parts of the BASE such as games or uucp.

Basically look for explicitely created variables that STOP
the compilation/use of certain subsystems that are often not
needed/wanted.  E.G. in /usr/src/gnu/libexec/Makefile (please
notes that uuencode/uudecode are NOT affected.

--- /usr/src/gnu/libexec/Makefile.orig	Tue Mar 21 14:35:18 2000
+++ /usr/src/gnu/libexec/Makefile	Tue Apr 11 23:16:51 2000
@@ -1,6 +1,8 @@
 #	$OpenBSD: Makefile,v 1.3 1999/02/01 05:37:27 todd Exp $
+.ifdef NOUUCP
 SUBDIR=	uucp
 .if (${MACHINE_ARCH} == "mips") || make(clean) || make(cleandir) || make(obj)
 SUBDIR+= ld.so

I've done similiar for games (NOGAMES).  If the variables are
defined in /etc/mk.conf, then it will get ignored.

Frankly, I'm running machines that I don't want or need some of
these systems on my production machines.  One issue is space
on some of the older ones, others are the run the minimum you

Perhaps, long term, we can tag some of the other tools that are
extra to a minimal system.  This might include tagging as "DEVEL"
tools like yacc, lint, egcs, and so forth.  Useful on many systems,
but undesirable on (my) production systems.

Again, DEFAULT behavior is UNCHANGED.  You must define a new variable
to STOP these from being built.

Anyhow, if the developers are at all interested, I'd love to start
supplying the (simple) patches.  UUCP and GAMES were the obvious
ones to test the waters with.


Visit your host, monkey.org