Re: Importing packages into CVS

On Tue, Mar 27, 2007 at 05:23:16PM -0700, Joshua Eichorn wrote: > >>>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. > >>> > My point is that this is solvable. It is only really solvable, using CVS, in a way in which the cvs.php.net version should be considered read-only. > >>>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. > >>> > Commiting to a fork could be a reasonable short term solution if the > maintainer wasn't available for whatever reason, and an emergency bug > fix was needed. While this is a valid case, I think it's exceptionally rare. If this is the only true reason to mirror copies of active code on cvs.php.net, I don't think it's worth the effort. > >>>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. > >>> > This code is available in the tarballs but not easily accessible since > its all compressed, and has no tools associated with it. > > I think the biggest benefit is allowing for easy access to all the code > by QA scripts. I'm inclined to disagree with this, as well. Sure, it's nice for QA to 'cvs checkout pear/' to get all possible PEAR source code, but they could also use a system that does: for package in allPackages: extractPackageArchive() results += analyzePackage() cleanupPackage() -- Jon Parise (jon of php.net) :: The PHP Project (http://www.php.net/)