Re: Namespace pollution
I think that this proposed policy is too strict. It forbids several
commands already in widespread use on the system, and it forbids
program names from being a single (English?) word, which is
unreasonable, in my opinion.
Some command names that this policy forbids:
(Section 1) GnomeScott Mail MakeTeXMF MakeTeXPK MakeTeXTFM
MakeTeXmkdir MakeTeXnames R SuperProbe X X11 XF86Setup XF86_SVGA
XF86_VGA16 Xmark Xnest [ ae ar as at bc cc ci co cp dc dd df du ed ex
fc gs gv id js ld ln lp ls lz m4 mf mh mp mt mv mx nl nm ns od pr ps
rm sg sh sq su tr ul uz vi w wc wn
(Section 2) Every command on the system that has three or more
characters matches this! I suppose you mean '^...$'. In that case,
without considering `more than two such':
X11 a2p acs atq awk axe b2m bug c++ cal cam cat cmp col cpp csh cut
cvs dga dig dir dmp dos elm env eqn f2c fax fiz fmt frm ftp g++ gcc
gdb gpg gtt hcd hfs hls ico irc jre ksh ldd lex lha lpc lpq lpr mag
man mcd mev mft mmd mrd nex nvi ode pap pgp pgs pic pon pwd rcp rcs
red rsh rup s2p scp sed seq soa sox ssh ssl sum tac tar tbl tee tex
tgz tic toe top tty twm who x48 xdm xev xfd xfs xgc xmh xmp xon xrx
xsm xtp xwd xwn yes zip zoo
(Section 3) GnomeScott Mail MakeTeXMF MakeTeXPK MakeTeXTFM
MakeTeXmkdir MakeTeXnames R SuperProbe X X11 XF86Setup XF86_SVGA
XF86_VGA16 Xmark Xnest [ c++ c++filt checkerg++ flex++ g++ graph-X
ircII plot2X virmf.X xpostit+
(Section 4) animate answer apropos arch as at bash batch bison bitmap
bug calendar cam cancel cat clear column combine convert cut date
deity dialog dig display double echo editor eject elm emacs ex expand
factor false file find finger flex fold free from games gasp gawk
graph groups gulp head host identify import indent install jade join
kill last less locate logger login look lout lynx mail make man merge
messages mirror more mount newer nice ode pager panel paste patch ping
play red refer reset screen script size skill sleep slice sort spent
spline split states strings strip sum tail talk tangle tar test time
toe top touch true users vacation view wall watch weave which who
widget wish workman write yes zone zoo
At the very least, `sound technical reasons' needs to be clarified and
expanded. The policy needs a clear list of recognized exceptions,
along with rationales. I don't think that all of the commands above
need to be renamed.
And the `or any directory directly in /, /usr, or /var' is forbidden
by FSSTND anyway, right? Or is there something more behind this
clause?
Reply to: