mk nuke doesn't nuke shell scripts

[GoogleCodeExporter]

mk nuke fails in appl/demo/spree as appl/demo/spree installs only
a shell script, so as TARG is empty nuke-std target in mkdis fails with:

(cd spree; mk -k nuke)
rm -f *.dis *.sbl
cd /usr/inferno/dis/demo/spree; rm -f
usage: rm [-f|-i] [-dPRrvW] file ...
mk: cd /usr/inferno/dis/demo/spree; rm ...  : exit status=exit(1)

There other scripts left under dis/ after mk nuke, e.g.
dis/demo/chat/chatclient etc...

Original issue reported on code.google.com by v.usha...@gmail.com on 2 Mar 2007 at 1:53

[GoogleCodeExporter]

There are other incosistencies w.r.t mk nuke

. shell scripts checked in only under dis/ without a source (e.g. man, shutdown)

. stray dis/auth/proto/authquery.sbl

. assorted *.dis files, most of them are commented out in mkfiles in the
  source directories where corresponding .b files reside, e.g. dis/lib/tcl_tk.dis

It would be nice if mk nuke really nuked everything under dis (shell scripts),
and to purge from svn the dis files that are no longer built/installed.

Original comment by v.usha...@gmail.com on 2 Mar 2007 at 2:11

[GoogleCodeExporter]

it seemed more sensible that scripts were obviously their own source, but that 
hadn't been done throughout (eg, appl/svc), since the latter were earlier.  it 
might 
be better to put the scripts outside /dis and bind that directory into place 
(cf. /
$objtype and /rc on plan 9), but that can't be done until there's a more 
consistent 
handling of the user/application initial name space

meanwhile we'll track down the stray files.

Original comment by Charles....@gmail.com on 2 Mar 2007 at 5:54

• Changed state: MullingItOver