Date: Wed, 12 Sep 2012 06:31:58 -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: <1347456718.53705.YahooMailClassic@web111309.mail.gq1.yahoo.com> In-Reply-To: <5049EA50.4040001@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Fri, 9/7/12, Beat Gaetzi <beat@FreeBSD.org> wrote:=0A=0A> From= : Beat Gaetzi <beat@FreeBSD.org>=0A> Subject: [HEADS-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 FreeBSD ports is=0A> done in Subver= sion nowadays.=0A> For the sake of compatibility a Subversion to CVS export= er=0A> is=0A> in place which has some limitations. For CVSup mirroring=0A> = cvsup=0A> based on Ezm3 is used which breaks regularly especially on=0A> am= d64=0A> and with Clang and becomes more and more unmaintainable.=0A> =0A> F= or those reasons by February 28th 2013 the FreeBSD ports=0A> tree will=0A> = no longer be exported to CVS. Therefore ports tree updates=0A> via CVS=0A> = or CVSup will no longer available after that date. All users=0A> who use=0A= > CVS or CVSup to update the ports tree are encouraged to=0A> switch to=0A>= portsnap(8) [1] or for users which need more control over=0A> their ports= =0A> collection checkout use Subversion directly:=0A> =0A> % svn co https:/= /svn0.us-west.FreeBSD.org/ports/head /usr/ports=0A> =0A> and update a check= ed out repository using:=0A> =0A> % cd /usr/ports && svn update=0A> =0A> Ad= vanced users, or larger sites, might consider setting up a=0A> local=0A> sv= n mirror. Both for people doing direct checkouts and for=0A> people=0A> wan= ting to use a local mirror, they can access one of the=0A> public=0A> subve= rsion servers [2].=0A> =0A> How to set up a Subversion mirror using svnsync= (1) is=0A> described in=0A> the FreeBSD Committers Guide [3]. Initial seeds= to set up a=0A> svnsync=0A> mirror are provided on the FreeBSD FTP mirror = sites under=0A> /pub/FreeBSD/development/subversion/.=0A> =0A> Binary packa= ges for pkg_install are still provided via the=0A> FTP mirror=0A> network. = There is also pkgng which is a feature rich=0A> replacement tool=0A> for pk= g_install available in the ports tree under=0A> ports/ports-mgmt/pkg.=0A> P= ackages for pkgng are available on pkg.FreeBSD.org.=0A> =0A> To use pkg.Fre= eBSD.org at least pkgng 1.0 RC6 is needed and=0A> can be=0A> enabled in pkg= .conf like this (where ${ABI} is dependent on=0A> your=0A> system):=0A> PAC= KAGESITE=A0 =A0 =A0 =A0=A0=A0: http://pkg.freebsd.org/${ABI}/latest=0A>; SRV= _MIRRORS=A0 =A0 =A0 =A0=A0=A0: YES=0A> =0A> With pkgng 1.0 SRV_MIRRORS is e= nabled by default and no=0A> longer needs=0A> to be set explicitly. If pkgn= g prior to 1.0 RC6 is used=0A> http://pkgbeta.FreeBSD.org can be used as pa= ckagesite=0A> instead.=0A> =0A> Please keep im mind that the pkgng infrastr= ucture is still=0A> considered=0A> as beta. More information about pkgng ca= n be found at=0A> http://wiki.FreeBSD.org/pkgng and https://github.com/pkgn= g/pkgng.=0A> =0A> Beat, on behalf of portmgr@=0A> =0A> [1] http://www.FreeB= SD.org/doc/handbook/updating-upgrading-portsnap.html=0A> [2] http://www.Fre= eBSD.org/doc/handbook/mirrors-svn.html=0A> [3]=0A> http://www.FreeBSD.org/d= oc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html=0A> ___= ____________________________________________=0A> freebsd-ports@freebsd.org= =0A> mailing list=0A> http://lists.freebsd.org/mailman/listinfo/freebsd-por= ts=0A> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.= org"=0A> =0A[1] Should not this go in UPDATING now for persons who have it= =0Aset in cron and do not read this list? Thus they would have time=0Ato p= repare adequately or to ask questions at the minimum.=0A=0A[2] Any URL of s= ites which would be portsnap or svn updated, yet=0Aexport via a cvs server = for persons to continue using csup/cvsup?=0A=0AI had a random thought that = this change could be delayed one release=0Aso that csup could depend upon a= new .so. "on purpose" in v10 that=0Awould notify the user somehow that it = is deprecated in v11... but=0Athat neglects cvsup... =0A=0AJ. Bouquet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1347456718.53705.YahooMailClassic>