From owner-freebsd-current Sun Sep 24 16:30:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA21381 for current-outgoing; Sun, 24 Sep 1995 16:30:36 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA21376 for ; Sun, 24 Sep 1995 16:30:33 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA04144; Sun, 24 Sep 1995 16:27:06 -0700 From: Terry Lambert Message-Id: <199509242327.QAA04144@phaeton.artisoft.com> Subject: Re: kernel versions and config's rm -rf To: rgrimes@GndRsh.aac.dev.com (Rodney W. Grimes) Date: Sun, 24 Sep 1995 16:27:06 -0700 (MST) Cc: terry@lambert.org, fenner@parc.xerox.com, current@freebsd.org In-Reply-To: <199509242205.PAA01453@GndRsh.aac.dev.com> from "Rodney W. Grimes" at Sep 24, 95 03:05:28 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 906 Sender: owner-current@freebsd.org Precedence: bulk > > > I like this, it is far more appropriate than an rm -rf, but should be > > > reduced even further to just ``make clean; rm *.h'' and > > > the clean: target had better do the right things. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ ... ] > I think I covered your minor issue below quite well above. It doesn't; otherwise the newversion and config could get by without explicitly deleting everything. That was my point exactly. A partial fix that just adds more explicit dependencies on a broken procedure (which the prepatched code is, and which is not fixed post-patch) is a bad fix. At best, it's work that has been done out of order. At worst, it's further breakage along the same lines as the existing breakage in the dependency graph. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.