Time to deprecate ports/net/cvsupit?
Jordan Hubbard
jkh at queasyweasel.com
Tue May 6 16:18:35 PDT 2003
I'm posting this to the -hackers list since Kris and my discussion on
this topic hasn't generated any feedback on -ports so far and he
assures me that people are actually still interested in cvsupit, or at
least the functionality it represents.
To make a long story short, cvsupit is another of my supposed
short-term hacks (when will I learn?) that's long outlived its
creator's desire to keep it on life support and was not written with
long-term maintainability in mind at all. Each and every release or
branch of FreeBSD basically requires hand-editing a shell script, as
does any change in the cvsup mirrors, in order to keep the port working
and/or relevant.
So, I put it to all of you: If people really do think that a
"graphical" configuration front-end to cvsup is a good thing for the
long term then one of those people should also volunteer to step
forward and write some custom scripts to create *dynamic* content which
uses release-engineer provided metadata to put up UI which is relevant
to whatever releases/branches of FreeBSD are currently shipping. For
extra points, it should also get a master list of cvsup servers from
somewhere (shared with the handbook?) so that this changes
automatically as servers are added/deleted.
I personally plan on cvs deleting the cvsupit port in another week or
two and hope that nobody feels compelled to simply resurrect it and put
this pathetic bit of zombie software back on life-support rather than
tackling the problem from scratch and doing it RIGHT this time.
Yours for a better (and cleaner/more maintainable) FreeBSD...
- Jordan
More information about the freebsd-hackers
mailing list