From: presotto@closedmind.org
To: 9fans@cse.psu.edu
Subject: Re: Plan 9 annoyances (was: Re: [9fans] mv vs cp)
Date: Mon, 15 Oct 2001 10:45:47 -0400 [thread overview]
Message-ID: <20011015144550.23C1219A2C@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 58 bytes --]
I agree that the distinction is hardly worth the effort.
[-- Attachment #2: Type: message/rfc822, Size: 3029 bytes --]
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: Re: Plan 9 annoyances (was: Re: [9fans] mv vs cp)
Date: Mon, 15 Oct 2001 01:30:19 -0700 (PDT)
Message-ID: <200110150830.f9F8UJa82006@ducky.net>
>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".
next reply other threads:[~2001-10-15 14:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 14:45 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-16 19:46 forsyth
2001-10-15 18:36 David Gordon Hogan
2001-10-11 15:17 forsyth
2001-10-11 19:29 ` Micah Stetson
2001-10-11 12:21 bwc
2001-10-11 11:20 forsyth
2001-10-12 9:23 ` pac
2001-10-10 10:50 forsyth
2001-10-10 13:06 ` Sam Hopkins
2001-10-10 10:45 forsyth
2001-10-09 17:08 forsyth
2001-10-10 8:56 ` Thomas Bushnell, BSG
2001-10-10 9:55 ` Mike Haertel
2001-10-10 10:09 ` Lucio De Re
2001-10-11 9:10 ` Thomas Bushnell, BSG
2001-10-09 16:55 anothy
2001-10-09 15:23 anothy
2001-10-09 14:56 anothy
2001-10-09 13:18 bwc
2001-10-10 8:57 ` Douglas A. Gwyn
2001-10-09 10:55 rog
2001-10-09 11:50 ` George Michaelson
2001-10-09 10:12 forsyth
2001-10-09 16:18 ` Thomas Bushnell, BSG
2001-10-08 21:24 Russ Cox
2001-10-08 21:21 rog
2001-10-08 20:17 Russ Cox
2001-10-14 19:54 ` Mike Haertel
2001-10-15 6:46 ` Boyd Roberts
2001-10-15 8:30 ` Mike Haertel
2001-10-08 16:51 anothy
2001-10-09 9:04 ` Thomas Bushnell, BSG
2001-10-09 9:04 ` Ralph Corderoy
2001-10-10 8:56 ` Douglas A. Gwyn
2001-10-08 6:27 [9fans] mv vs cp Lucio De Re
2001-10-08 8:38 ` Plan 9 annoyances (was: Re: [9fans] mv vs cp) Mike Haertel
2001-10-08 9:08 ` Lucio De Re
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011015144550.23C1219A2C@mail.cse.psu.edu \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).