> [...issues with mkstr...]
> Distributing such crappy programs hurts the reputation of NetBSD
> delivering quality software,
Does it? I have yet to hear of anyone thinking any the less of NetBSD
for including mkstr, excepting any directly derived from this thread.
I was not even aware NetBSD shipped anything called mkstr until I saw
this thread.
> therefore it should be removed.
I have experimented with it and find that what it actually does is not
what the manpage led me to think it does - though I can see a close
enough relation that I think I could write an accurate manpage.
If it is not in fact in live use, what NetBSD does with it matters
somewhere between "very little" and "not at all".
If it is in fact in live use, someone obviously has found a use for it
despite its various string-mangling bugs and misleading documentation.
If this call were mine to make? I would add a few lines to mkstr to
print a message to stderr, maybe something along the lines of
NetBSD is considering removing mkstr; please contact
tech-userlevel@netbsd.org if you would like to see it
maintained. To suppress this message in the meantime, set
MKSTR_SUPPRESS_MESSAGE in the environment.
Then, after a couple of releases, and of course assuming nobody
squawks, dump it.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
