From owner-freebsd-current  Sun Sep 24 23:45:41 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id XAA03540
          for current-outgoing; Sun, 24 Sep 1995 23:45:41 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA03535
          for <current@FreeBSD.ORG>; Sun, 24 Sep 1995 23:45:33 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA00867; Mon, 25 Sep 1995 16:42:25 +1000
Date: Mon, 25 Sep 1995 16:42:25 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199509250642.QAA00867@godzilla.zeta.org.au>
To: fenner@parc.xerox.com, terry@lambert.org
Subject: Re: kernel versions and config's rm -rf
Cc: current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

>> The other solution that I was considering was reading the number out of
>> the "version" file before the "rm -rf" and then writing it out again
>> afterwards.  I'll write that instead, if it would make you more comfortable.

>Yes, please.  This keeps the breakage in the dependency graph (which
>will hopefully some day be fixed) sperate from the config, which
>removes far more than it really has too, but does so because the
>dependecy graph breakage is hidden from it.

Arrgh.  The dependencies are all contained in .depend and Makefile.
`make clean' doesn't remove the former so you have to do it.  `config'
touches the latter (even when it shouldn't) so you don't have to remove
it.  The following steps are sufficient:

	cd /sys/compile/FOOKERNEL
	make clean
	rm -f .depend
	cd /sys/i386/conf
	# in case config is still broken:
	export NO_CONFIG_CLOBBER='config clobbering is braindamaged'
	config ...

Removing *.c and *.h has no effect other than to remove old unreferenced
rubbish.

>I'm wondering at the existance of compile time optioning in the first
>place.  Really, it exists because the device driver and other subsystems
>don't have explicit registration mechanisms that don't depend on static
>data.

No, it exists because static configuration is easier to implement and
has less bloat.

Bruce