From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Haertel 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> Date: Mon, 15 Oct 2001 01:30:19 -0700 Topicbox-Message-UUID: 08add52e-eaca-11e9-9e20-41e7f4b1d025 >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".