Re: Importing packages into CVS

Alexey Borzov wrote: > Hi, > > Christian Weiske wrote: >> After it seems that most people agreed that having all packages in our >> CVS, I would like to do the work and import every version of every >> package currently not in PEAR CVS into CVS. >> > > Let me give a more verbose version of my attitude to this particular idea. > > The *real* problem we had is disappearing releases: this bites me > directly, since my HTML_Template_Sigma package uses old PHPUnit for its > unit testing needs. Thus without old PHPUnit package on PEAR website > these tests cannot be run at all. Of course I can redo them for current > PHPUnit, but it is a bit stupid to require a PHP 5.2+ package for > testing of PHP 4 one. > > Now, is your "solution" helping at all? No, 'cause there still won't be > any PHPUnit package and person wishing to test HTML_Template_Sigma will > need to checkout PHPUnit from CVS and jump through a number of hoops to > install / use it. > > On the other hand, if PHPUnit releases *were* present on PEAR website, > anyone wishing to have them in CVS would be able to import them to > whatever CVS he likes. > > So "just mirroring the releases" helps nothing at all, *if* we prevent > disappearing packages in the future. If we aren't "just mirroring" but > require using PHP CVS service, then this idea should go through a more > formal channel (like, RFC) rather than "it seems that most people > agreed". You'd be surprised on the number of changes you'd have to make > until there will be a real agreement. Hi Alexey and company, First, everyone has raised very good objections to the original proposals, and I think we can resolve this quite easily by NOT touching packages like the Horde packages. I'm sorry the original proposal blew up, I'll take the blame/heat entirely for peoples concerns. I think that there is a way to solve the issue that is bothering me and the one bothering Alexey, let me elaborate below. I see two separate issues: 1) disappearing releases 2) orphaned packages that do not have CVS at cvs.php.net There is no way to prevent disappearing packages at all. As it stands, someone will have to take the time to reconstruct the PHPUnit package from CVS. It will probably have to be me since no one else has stepped forward. Let's just say I have the patience to do this kind of bullshit once in my life. Imagine what would happen if the PHPUnit package were *not* hosted at cvs.php.net. Reconstructing releases would be quite literally impossible. One solution is to save a copy of all deleted releases "just in case." This is impractical for many reasons, but if any of you have a better suggestion I would love to hear it. As for orphaned packages, this is far simpler: if the package is not maintained, and the RCS is external or non-existent, there is no other alternative, development is essentially over unless it is imported into cvs.php.net. To resolve the issues raised on both sides of the fence, can we take the following steps: If a package is unmaintained, its code must be imported into CVS at cvs.php.net so that another maintainer can take over the lead role, and QA releases can be made until that point in time when a new maintainer steps forward If a package is maintained, no changes will be made to anything. If a maintainer decides to move a package out of pear.php.net, the package must be forked and added to cvs.php.net, and all old releases will not be deleted from pear.php.net. Specifically, packages mentioned by Chuck in his first email that are maintained at Horde are not in any real danger of being unmaintained, and so would not have to worry about a thing unless Horde decides to drop them, and then there would be no hard feelings having them imported since Horde would no longer want to maintain them (do I have this idea right in my head?). Does this satisfy everyone's worries? I'm most concerned with #2, #1 is anomalous to PHPUnit, most packages just end not with a bang but with a whimper. I'd really like to see the unmaintained packages available for adoption. As I understand it, that is the primary goal of this new thing. Thanks, Greg