Re: Importing packages into CVS

Jon Parise wrote:

On Tue, Mar 27, 2007 at 01:40:34PM -0400, Chuck Hagenbuch wrote:

For active packages such as the ones you've listed, it may make sense to provide some kind of automated system for synchronizing the repositories, so that cvs.php.net is up-to-date with changes to the primary repository. Perhaps, since Christian proposed the change, he would be willing to set up a synchronization cron job on one of his servers?

Well anyone is certainly welcome to mirror Horde's anoncvs repository I guess. As to replicating commits, that seems like a bit much. And in terms of redundancy, aren't all of the releases already archived on pear.php.net?

Indeed. I agree with Chuck here. 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.

-josh