Date: Wed, 27 Jun 2012 14:52:16 -0700 From: Jason Helfman <jhelfman@e-e.com> To: Kevin Oberman <kob6558@gmail.com> Cc: ports@freebsd.org, Thomas Abthorpe <tabthorpe@freebsd.org> Subject: Re: [HEADS UP] Ports tree migration to Subversion Message-ID: <20120627215215.GS47920@dormouse.experts-exchange.com> In-Reply-To: <CAN6yY1s4e-6W9EvWn7EpC7OHmk71CY5EqjPigdJ8G-6qM9ZkMw@mail.gmail.com> References: <20120627173011.GA50088@freefall.freebsd.org> <CAN6yY1s4e-6W9EvWn7EpC7OHmk71CY5EqjPigdJ8G-6qM9ZkMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 27, 2012 at 02:47:34PM -0700, Kevin Oberman thus spake: >On Wed, Jun 27, 2012 at 10:30 AM, Thomas Abthorpe <tabthorpe@freebsd.org> wrote: >> The FreeBSD ports tree will migrate from CVS to Subversion soon. The >> anticipated date for the migration is July 14th. This will have no impact >> for ports tree users as there will be a SVN to CVS exporter. >> >> Please note that cvsup will still work after the migration. Nevertheless >> c(v)sup is pretty dated so you may want to see if portsnap(8) will fit your >> needs. >> >> Beat and Thomas >> on behalf of portmgr@ >> >> http://blogs.freebsdish.org/portmgr/2012/06/27/ports-tree-migration-to-subversion/ > >While portsnap has several advantages over csup, it is unusable in my >case because I have always maintained local mods to ports in the ports >tree and portsnap neatly removes them. I may move to using svn to >maintain my own copy of the tree and update the working directory >where I can keep my customizations. You may want to look at the manpage for portsnap.conf and see how advantageous it may be to use the REFUSE option. -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120627215215.GS47920>