From owner-cvs-usrsbin Wed Nov 29 08:57:36 1995
Return-Path: owner-cvs-usrsbin
Received: (from root@localhost)
by freefall.freebsd.org (8.6.12/8.6.6) id IAA01012
for cvs-usrsbin-outgoing; Wed, 29 Nov 1995 08:57:36 -0800
Received: from skiddaw.elsevier.co.uk (skiddaw.elsevier.co.uk [193.131.222.60])
by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA01002
; Wed, 29 Nov 1995 08:57:21 -0800
Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by skiddaw.elsevier.co.uk (8.6.12/8.6.12) with ESMTP id QAA17384; Wed, 29 Nov 1995 16:55:33 GMT
Received: from isis by snowdon with SMTP (PP); Wed, 29 Nov 1995 16:51:50 +0000
Received: (from dpr@localhost) by isis (SMI-8.6/8.6.12) id QAA17657;
Wed, 29 Nov 1995 16:53:35 GMT
From: Paul Richards
Message-Id: <199511291653.QAA17657@isis>
Subject: Re: cvs commit: src/usr.sbin/config Makefile main.c
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Wed, 29 Nov 1995 16:53:35 +0000 (GMT)
Cc: wollman@lcs.mit.edu, wollman@freefall.freebsd.org,
CVS-committers@freefall.freebsd.org, cvs-usrsbin@freefall.freebsd.org
In-Reply-To: <8337.817662882@time.cdrom.com> from "Jordan K. Hubbard" at Nov 29, 95 08:34:42 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-cvs-usrsbin@FreeBSD.ORG
Precedence: bulk
In reply to Jordan K. Hubbard who said
>
> You're saying to me that you believe the dependency information to be
> updated properly by config, even when adding or deleting lines to the
> config file? E.g. it's possible for me to screw around with my config
> file, re-run config and get a decent kernel out of what I build?
The dependency information isn't updated at all.
The trick is knowing that the changes don't cross files that aren't
dependant upon each other :-)
You can make lots of changes to config files that are "within" a
particular dependency graph. Probably more changes fall in this category
than actually cross dependency graphs though I wouldn't like to quantify
that statement.
Fiddling with device drivers never seems to require clobbering a
previous config, for instance, since all the files that need to be
rebuilt are actually touched by the config process and the dependency for
those files is correct.
> And please don't answer with some inane "the experienced user will
> know when to blow away /sys/compile/" response since I already
> *know* from bitter experience that this is most emphatically not the
> case.
You're obviously changing lines that have bad effects :-) The fact is, the
experienced use does know.
One thing that almost always will screw you is option settings since
these translate to defines and not all the files that would be
affected by that define will get touched by a config so they don't get
rebuilt with the new settings. A very difficult problem to solve and
not one likely to ever get done by any of the current contributers.
Since that is the "underlying" problem I don't see that addressing it
will bear any fruit. You just have to understand it and be aware of it.
I guess most of use have all the NOCLOBBER options set :-)
--
Paul Richards. Originative Solutions Ltd.
Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk
Phone: 0370 462071 (Mobile), +44 1225 447500 (work)