Re: Importing packages into CVS

On Tue, Mar 27, 2007 at 05:12:02PM -0700, Joshua Eichorn wrote: > >What is the point of hosting a _copy_ of the source code on > >cvs.php.net? PEAR currently permits active development to occur in an > >external source control repository so the cvs.php.net would always be > >out-of-date. > > > >Do you want it to be hosted on cvs.php.net as a reference resource? > >The code will never be current, and the active external repository can > >already be used as a reference. > > > >Do yo want to allow PEAR QA folks to commit changes to a package's > >code? The code will become forked from the active development line. > > > >Do you want to archive a historic copy of the code, perhaps on a > >per-release basis? pear.php.net already has a copy of the source code > >on a per-release basis. > > > >I'm not seeing the benefit. > > > Maybe this would work with a script to automatically sync on commit from > the external repo. I don't see the user otherwise. That would be a potential mechanism to accomplish the mirroring operation. I'm suggesting that there is no reason to pursue mirroring in the first place (and therefore no reason to write such a script). Please: let's not proceed too quickly until someone can provide good responses to the questions that I've raised above. -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)