removing CVS in Handbook Updating and Upgrading chapter

Isaac (.ike) Levy ike at blackskyresearch.net
Sat Jan 26 23:10:26 UTC 2013


On Jan 25, 2013, at 2:12 PM, Warren Block wrote:
>>> CVS is going away soon, and we should not be advising people to start using them now.
>>> This diff entirely removes cvsup, csup, and CVS references from the Updating and Upgrading chapter.  SVN URLs are also changed to the preferred form and links to the SVN mirrors are added.
>>> Rendered: http://www.wonkity.com/~wblock/temp/cuttingedge-nocvs.html
>>>   Diff: http://www.wonkity.com/~wblock/temp/cuttingedge-nocvs.diff

Regarding src, this appears to be jumping the gun quite a bit, with possibly bad consequences:

  + ports, cvsup access end-of-lifed Feb 28
   (cool! drop cvs/cvsup references for it)
  - source, cvsup deprecated - no end-of-life date set
   (until canonical replacement is in place)

Instead of replacing *all* CVS urls with SVN, I would like to advise you to merely make note of cvsup being deprecated for src?

Not sure if I need to explain this, but:
For a large number of system integrators, building userland/kernel from source is critical.
Most of these builds happen before ports/pkg get installed, (if they even do).  The current state of SVN, binary packages, ports mechanism changes, and otherwise- all make for some nasty chicken/egg problems for many systems integrators.

There are several simplifying projects in play, (there was a lively/lengthy thread on freebsd-stable@ this week, and some action over in ports to immeadiately simplify some notable SVN dependency messes...)
http://lists.freebsd.org/pipermail/freebsd-stable/2013-January/071798.html

This sort of dependency-free simplicity, is what drives a huge number of FreeBSD installs.

--
With that, until cvsup actually has an end-of-life date, cvsup/csup can not be removed completely from docs, whenever it refers to src.

Thoughts?

Best,
.ike




More information about the freebsd-doc mailing list