Date: Wed, 23 Mar 2011 09:03:59 -0400 From: John Baldwin <jhb@freebsd.org> To: Garrett Cooper <gcooper@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: svn commit: r219788 - head/release Message-ID: <201103230903.59651.jhb@freebsd.org> In-Reply-To: <AANLkTim92LpSA%2BZuy3WQjUTEDK=3Y7kmtMO_B0na=kLu@mail.gmail.com> References: <201103192306.p2JN6Inv037425@svn.freebsd.org> <AANLkTim92LpSA%2BZuy3WQjUTEDK=3Y7kmtMO_B0na=kLu@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, March 19, 2011 7:10:40 pm Garrett Cooper wrote: > On Sat, Mar 19, 2011 at 4:06 PM, Nathan Whitehorn > <nwhitehorn@freebsd.org> wrote: > > Author: nwhitehorn > > Date: Sat Mar 19 23:06:17 2011 > > New Revision: 219788 > > URL: http://svn.freebsd.org/changeset/base/219788 > > > > Log: > > Add support for checking out ports and doc trees from a CVS repository, > > in addition to CVSUP, and add support for alternate SVN roots for src. > > > > Requested by: jhb > > Although this seems good and all, wouldn't it make sense to split off > the pulling infrastructure into separate scripts so that someone could > have hooks to do: > > - pre-pull (create paths, whatever) > - pull > - post-pull (patch?) > > That way someone could choose any arbitrary SCM (git, hg, etc), > specify necessary configuration files, and apply local patches as > necessary. The old release(7) infrastructure did do that (see things like LOCAL_PATCHES, EXTSRCDIR, LOCAL_SCRIPTS, etc.). However, we should definitely streamline the case for the tools that re@ will actually use for official releases (doc and ports from CVS, src from either CVS or SVN). -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201103230903.59651.jhb>