>>>> "Valdis" == Valdis Kletnieks
<Valdis.Kletnieks(a)vt.edu> writes:
Valdis> On Sun, 21 Jan 2001 09:45:43 +0900, "Stephen J. Turnbull"
Valdis> said:
> I personally don't have a problem with undocumented cruft in
my
> .../bin directories
Valdis> Say hello to a sysadmin who's really anal-retentive about
Valdis> being able to identify where a random binary came from,
Valdis> and what its reason for being is. ;)
Hello to a sysadmin who's really anal-retentive about being able to
identify where a random binary came from, and what its reason for
being is. ;)
I know youse guys are out there. :-)
This isn't an election; if everybody but you says "I don't care" and
you say "I care (and others should, too)" convincingly, you win.
Convince me.
First off, I'm sorry, but I miswrote. What I really wanted to know
was "suppose we document it. Then do you care?" The installed dump
file implies it's part of XEmacs by its name. If this were properly
documented in Info, FAQ, INSTALL, NEWS, and Installation, would you
still object to this file being installed in .../bin?
Nicholas and Martin evidently object because it's not an executable
command. Is that the way you feel about it, or do you worry primarily
because it's undocumented?
Are there _tools_ that sweep bin directories for non-executable cruft
that would care, to anybody's knowledge? Is that a sufficiently good
idea that even if they _don't_ exist, someone should write one (and
probably will)?
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."