Re: Importing packages into CVS

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.