Date: Sat, 26 Jan 2013 21:26:10 -0500 From: Eitan Adler <lists@eitanadler.com> To: Warren Block <wblock@wonkity.com> Cc: freebsd-doc@freebsd.org Subject: Re: removing CVS in Handbook Updating and Upgrading chapter Message-ID: <CAF6rxg=_cih7rvDM7WcdRpksCvh7jF7LzeKE0qeO2RHPDw2JfA@mail.gmail.com> In-Reply-To: <alpine.BSF.2.00.1301261808410.2537@wonkity.com> References: <alpine.BSF.2.00.1301241510470.86451@wonkity.com> <alpine.GSO.1.10.1301251321400.9389@multics.mit.edu> <alpine.BSF.2.00.1301251154450.5025@wonkity.com> <1359241802-3572135.75152325.fr0QN9mrI032137@rs149.luxsci.com> <alpine.BSF.2.00.1301261808410.2537@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 January 2013 21:05, Warren Block <wblock@wonkity.com> >> 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. We should certainly be striving to remove references to CVS from as many places as possible. I have no objections to leaving one (obviously marked) chapter about the old way of doing things. > This part of the Handbook refers to fetching source for -CURRENT or -STABLE. > We should not be suggesting CVS to new users who want to run development > versions of FreeBSD. It's a misdirection, like a Perldoc-esque "here's an > example, but you should never, ever do this". > > Existing CVS users already know how to use it, being existing and all. So > the removal of CVS information from this chapter should not harm anyone > already using it and should help by not steering newcomers to the wrong > tool. +1 -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=_cih7rvDM7WcdRpksCvh7jF7LzeKE0qeO2RHPDw2JfA>