Date: Wed, 12 Sep 2012 07:14:27 -0700 (PDT) From: Jeffrey Bouquet <jeffreybouquet@yahoo.com> To: freebsd-ports@FreeBSD.org, Beat Gaetzi <beat@FreeBSD.org> Subject: Re: [HEADS-UP] Announcing the end of port CVS Message-ID: <1347459267.19692.YahooMailClassic@web111316.mail.gq1.yahoo.com>
next in thread | raw e-mail | index | archive | help
=0A--- On Wed, 9/12/12, Jeffrey Bouquet <jeffreybouquet@yahoo.com> wrote:= =0A=0A> From: Jeffrey Bouquet <jeffreybouquet@yahoo.com>=0A> Subject: Re: [= HEADS-UP] Announcing the end of port CVS=0A> To: freebsd-ports@FreeBSD.org,= "Beat Gaetzi" <beat@FreeBSD.org>=0A> Date: Wednesday, September 12, 2012, = 6:31 AM=0A> =0A> =0A> --- On Fri, 9/7/12, Beat Gaetzi <beat@FreeBSD.org>=0A= > wrote:=0A> =0A> > From: Beat Gaetzi <beat@FreeBSD.org>=0A> > Subject: [HE= ADS-UP] Announcing the end of port CVS=0A> > To: freebsd-ports@FreeBSD.org= =0A> > Date: Friday, September 7, 2012, 5:36 AM=0A> > The development of Fr= eeBSD ports is=0A> > done in Subversion nowadays.=0A> > For the sake of com= patibility a Subversion to CVS=0A> exporter=0A> > is=0A> > in place which h= as some limitations. For CVSup=0A> mirroring=0A> > cvsup=0A> > based on Ezm= 3 is used which breaks regularly especially=0A> on=0A> > amd64=0A> > and wi= th Clang and becomes more and more=0A> unmaintainable.=0A> > =0A> > For tho= se reasons by February 28th 2013 the FreeBSD=0A> ports=0A> > tree will=0A> = > no longer be exported to CVS. Therefore ports tree=0A> updates=0A> > via = CVS=0A> > or CVSup will no longer available after that date. All=0A> users= =0A> > who use=0A> > CVS or CVSup to update the ports tree are encouraged= =0A> to=0A> > switch to=0A> > portsnap(8) [1] or for users which need more = control=0A> over=0A> > their ports=0A> > collection checkout use Subversion= directly:=0A> > =0A> > % svn co https://svn0.us-west.FreeBSD.org/ports/hea= d /usr/ports=0A> > =0A> > and update a checked out repository using:=0A> > = =0A> > % cd /usr/ports && svn update=0A> > =0A> > Advanced users, or larger= sites, might consider setting=0A> up a=0A> > local=0A> > svn mirror. Both = for people doing direct checkouts and=0A> for=0A> > people=0A> > wanting to= use a local mirror, they can access one of=0A> the=0A> > public=0A> > subv= ersion servers [2].=0A> > =0A> > How to set up a Subversion mirror using sv= nsync(1) is=0A> > described in=0A> > the FreeBSD Committers Guide [3]. Init= ial seeds to set=0A> up a=0A> > svnsync=0A> > mirror are provided on the Fr= eeBSD FTP mirror sites=0A> under=0A> > /pub/FreeBSD/development/subversion/= .=0A> > =0A> > Binary packages for pkg_install are still provided via=0A> t= he=0A> > FTP mirror=0A> > network. There is also pkgng which is a feature r= ich=0A> > replacement tool=0A> > for pkg_install available in the ports tre= e under=0A> > ports/ports-mgmt/pkg.=0A> > Packages for pkgng are available = on pkg.FreeBSD.org.=0A> > =0A> > To use pkg.FreeBSD.org at least pkgng 1.0 = RC6 is needed=0A> and=0A> > can be=0A> > enabled in pkg.conf like this (whe= re ${ABI} is=0A> dependent on=0A> > your=0A> > system):=0A> > PACKAGESITE= =A0 =A0 =A0 =A0=A0=A0: http://pkg.freebsd.org/${ABI}/latest=0A>; > SRV_MIRRO= RS=A0 =A0 =A0 =A0=A0=A0: YES=0A> > =0A> > With pkgng 1.0 SRV_MIRRORS is ena= bled by default and=0A> no=0A> > longer needs=0A> > to be set explicitly. I= f pkgng prior to 1.0 RC6 is=0A> used=0A> > http://pkgbeta.FreeBSD.org can b= e used as packagesite=0A> > instead.=0A> > =0A> > Please keep im mind that = the pkgng infrastructure is=0A> still=0A> > considered=0A> > as beta. More = information about pkgng can be found at=0A> > http://wiki.FreeBSD.org/pkgng= and https://github.com/pkgng/pkgng.=0A>; > =0A> > Beat, on behalf of portmg= r@=0A> > =0A> > [1] http://www.FreeBSD.org/doc/handbook/updating-upgrading-= portsnap.html=0A> > [2] http://www.FreeBSD.org/doc/handbook/mirrors-svn.htm= l=0A> > [3]=0A> > http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/commi= tters-guide/subversion-primer.html=0A> > __________________________________= _____________=0A> > freebsd-ports@freebsd.org=0A> > mailing list=0A> > http= ://lists.freebsd.org/mailman/listinfo/freebsd-ports=0A> > To unsubscribe, s= end any mail to "freebsd-ports-unsubscribe@freebsd.org"=0A> > =0A> [1] Shou= ld not this go in UPDATING now for persons who have=0A> it=0A> set in cron = and do not read this list?=A0 Thus they would=0A> have time=0A> to prepare = adequately or to ask questions at the minimum.=0A> =0A> [2] Any URL of site= s which would be portsnap or svn updated,=0A> yet=0A> export via a cvs serv= er for persons to continue using=0A> csup/cvsup?=0A> =0A> I had a random th= ought that this change could be delayed one=0A> release=0A> so that csup co= uld depend upon a new .so. "on purpose" in=0A> v10 that=0A> would notify th= e user somehow that it is deprecated in=0A> v11... but=0A> that neglects cv= sup... =0A> =0A> J. Bouquet=0A> ___________________________________________= ____=0A> freebsd-ports@freebsd.org=0A> mailing list=0A> http://lists.freebs= d.org/mailman/listinfo/freebsd-ports=0A> To unsubscribe, send any mail to "= freebsd-ports-unsubscribe@freebsd.org"=0A> =0A=0AAs an example of a problem= they may encounter, I am stuck at=0Acrafting a solution (a .svn or portsna= p ports tree, which I =0Aunderstand may not allow (at least without specifi= c=0Acommands to "version" them...) local log files, local=0AMakefile.local,= etc...) =0A=0AAnd a ports tree which includes many=0Aof the latter. =0A=0A= It seems it would be somewhat of a three-way merge=0Awhich at many points w= ould be not adequately scripted, since=0Acopies from the newer (.svn, ports= nap) may not be adequately mirrored to the=0Amore-files-included (as above)= "final working ports tree", etc, unless it=0Aspecifically copied/gcp'd/rsy= nc'd different types of directories=0Awithin the tree (find -depth, /files/= , /src/, etc etc...) so as=0Ato remove as well as add files depending upon = the location of=0Athe directory within the port's PWD. =0AIt seems doable, = but at the expense of many many hours of=0Ascripting. Unless someone's don= e it already and put up a guide=0Asomewhere. =0A=0AOr I'm approaching it wr= ong, and simply want a ports tree server=0Aon the network... or some near-e= quivalent.=0A=0AApologies if there is some simple step/solution that I read= and=0Ahave not comprehended in a man page already, or a wiki page, or=0Aeq= uivalent.=0A=0AAgain, I see this as impacting more than just a few of some = admin's who=0Ause csup/cvsup as a matter of course, and may have a few =0Ac= ritical FreeBSD machines in a large infrastructure, or many=0Ain a smaller = infrastructure, and their updating procedure=0Amay thus stall irrevocably (= even worse, a remote upgrade one=0Aversion to another, or an early version = 9 to a later version 9,=0Aand a few hours of downtime to cvsup, say 2-3 am = and some may=0Adiscover the command no longer works... maybe breaking some= =0Aprocess of site (or router) (or firewall) (or network...) ...)=0A=0AJ. B= ouquet=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1347459267.19692.YahooMailClassic>