From owner-freebsd-current Mon Sep 25 13:02:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA20544 for current-outgoing; Mon, 25 Sep 1995 13:02:18 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA20521 for ; Mon, 25 Sep 1995 13:00:09 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA10311; Mon, 25 Sep 1995 13:58:01 -0600 Date: Mon, 25 Sep 1995 13:58:01 -0600 From: Nate Williams Message-Id: <199509251958.NAA10311@rocky.sri.MT.net> To: Terry Lambert Cc: wollman@lcs.mit.edu (Garrett A. Wollman), current@freebsd.org Subject: Re: kernel versions and config's rm -rf In-Reply-To: <199509251859.LAA05603@phaeton.artisoft.com> References: <9509251502.AA12642@halloran-eldar.lcs.mit.edu> <199509251859.LAA05603@phaeton.artisoft.com> Sender: owner-current@freebsd.org Precedence: bulk Terry Lambert writes: > > > The reason for this behaviour in the first place was an issue of > > > dependencies not being calculated correctly > > > > There is nothing wrong with the way the dependencies are calculated, .... > But make no mistake: this is not a "fix", it is a "workaround". > > *ONLY* the affected modules should have been rebuilt. The major problem faced is that is near impossible to determine dependencies on #ifdef'd code. When an options value changes, or is added/removed there is no way given the current scheme to know which files should be changed. This problem is faced by *ANY* C code developed, and it's only solution is to make everything dependent on the Makefile, which in term make re-compiling everything necessary for every new config, which is a non-solution. The issue of PTY's and others is a nice discussion point, but the you are still only solving one problem with many more exist which can't be solved as easily. Nate