From mboxrd@z Thu Jan  1 00:00:00 1970
From: presotto@closedmind.org
To: 9fans@cse.psu.edu
Subject: Re: Plan 9 annoyances (was: Re: [9fans] mv vs cp)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-empsviutuusxpmnxrysylhwqrg"
Message-Id: <20011015144550.23C1219A2C@mail.cse.psu.edu>
Date: Mon, 15 Oct 2001 10:45:47 -0400
Topicbox-Message-UUID: 08f5ac3c-eaca-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-empsviutuusxpmnxrysylhwqrg
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I agree that the distinction is hardly worth the effort.

--upas-empsviutuusxpmnxrysylhwqrg
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Mon Oct 15 04:31:27 EDT 2001
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Mon Oct 15 04:31:25 EDT 2001
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id 14DA019AAE; Mon, 15 Oct 2001 04:31:11 -0400 (EDT)
Delivered-To: 9fans@cse.psu.edu
Received: from ducky.net (unknown [199.26.172.91])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 01F0D19AA8
	for <9fans@cse.psu.edu>; Mon, 15 Oct 2001 04:30:21 -0400 (EDT)
Received: (from mike@localhost)
	by ducky.net (8.11.6/8.11.4) id f9F8UJa82006
	for 9fans@cse.psu.edu; Mon, 15 Oct 2001 01:30:19 -0700 (PDT)
	(envelope-from mike)
From: Mike Haertel <mike@ducky.net>
Message-Id: <200110150830.f9F8UJa82006@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: Plan 9 annoyances (was: Re: [9fans] mv vs cp)
In-Reply-To: <3BCA8652.F2CC96B7@strakt.com>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.6
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Mon, 15 Oct 2001 01:30:19 -0700 (PDT)

>Mike Haertel wrote:
>> i see no real reason for "mk nuke" to exist.  "mk clean" *almost* removes
>> every intermediate file; why not just fix it to get them all, and then
>> get rid of "mk nuke" entirely?
>
>No, 'nuke' and 'clean' serve two different purposes.  Both are aptly named.

Ok, here's an exercise for the reader...

After a full build of libraries and commands for the 386 target,
of all the thousands of files generated during the build, only
the following 17 files are *not* removed by "mk clean":

	/sys/src/ape/cmd/make/gram.c
	/sys/src/cmd/cc/cc.a8
	/sys/src/cmd/eqn/eqn.c
	/sys/src/cmd/9nfs/lib/lib.a8
	/sys/src/cmd/map/libmap/libmap.a8
	/sys/src/cmd/postscript/common/com.a8
	/sys/src/cmd/spell/amspell
	/sys/src/cmd/spell/brspell
	/sys/src/cmd/plot/libplot.a8
	/sys/src/cmd/cvs/lib/libcvs.a8
	/sys/src/cmd/cvs/zlib/libzlib.a8
	/sys/src/cmd/cvs/diff/libdiff.a8
	/sys/src/cmd/tex/tpic/picy.c
	/sys/src/cmd/tex/kpathsea/libkpathsea.a8
	/sys/src/cmd/tex/web2c/lib/lib.a8
	/sys/src/libthread/syms.386
	/sys/src/libscribble/syms

And here is the list of files left after a further "mk nuke":

	/sys/src/cmd/eqn/eqn.c
	/sys/src/cmd/map/libmap/libmap.a8
	/sys/src/cmd/cvs/lib/libcvs.a8
	/sys/src/cmd/cvs/zlib/libzlib.a8
	/sys/src/cmd/cvs/diff/libdiff.a8
	/sys/src/cmd/tex/tpic/picy.c
	/sys/src/cmd/tex/kpathsea/libkpathsea.a8
	/sys/src/cmd/tex/web2c/lib/lib.a8
	/sys/src/libthread/syms.386
	/sys/src/libscribble/syms

In other words, the difference between "mk clean" and "mk nuke" is
just 7 files in all of /sys/src.  (In addition, "mk nuke" does some
collateral damage outside /sys/src.)

So, please explain "different purposes" served by "mk clean" and "mk nuke".
--upas-empsviutuusxpmnxrysylhwqrg--