Re: Importing packages into CVS

Quoting Gregory Beaver <greg@chiaraquartet.net>:

Are you suggesting that these packages will be withdrawn from PEAR simply because we wish to keep a copy of the code in cvs.php.net? The packages already have bug trackers at pear.php.net, and all releases through pear.php.net as well as in Horde, there's no reason to do anything drastic. Please do not misinterpret this to be a wresting of code control away from the maintainer! It is an effort to provide redundancy and a fail-safe in the event that a package maintainer disappears.

Okay. The scope of the proposed changes, and any exceptions, was someone unclear from Christian's email.

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? -chuck -- "we are plastered to the windshield of the bus that is time." - Chris