Re: PHP 5

On Mon, 2002-02-11 at 16:10, Yavor Shahpazov wrote: > > ----- Original Message ----- > From: "Pierre-Alain Joye" <pajoye@wanadoo.fr> > To: <pear-dev@lists.php.net> > Sent: Sunday, February 10, 2002 7:18 PM > Subject: Re: [PEAR-DEV] PHP 5 > > > > > > On Sun, 10 Feb 2002 18:13:04 +0100 > > Wolfram Kriesing <lists@kriesing.de> wrote: > > > if we go for a 2-repository solution, how much extra work does it > > > mean? > > > does every bug have to be fixed twice? > > > do you have to check in changes twice? > > > > > > i think new classes should run on PHP5, the old once should be > > > converted to run under php5 and maintainence should be provided for > > > the php4 only on request/bug fixes, etc. new features may only go > > > into the php5 version. > > > It may be sounds cruel to those who use php4 but will everybody be > > > able to do double work? > > > or should there be some kind of deadline until when php4-packages are > > > maintained? > > 2 repository should be a good solution. To spare work, we can freeze the > php4 > > branch. Only bugs corrections could be applied in the php4 branch. New > features > > and code rewrite for the new one. > > > > This sounds ok fore new releases but what about peoples who have php4 and > want to download, the lates auth package for example, how will they know > that they have to get the auth-php4 package and not auth-latest package. I > think that for releases this is the way to do it but for packages will lead > to a lot of confutions;. I agree however that maintaining two repositories > is not a good solution. They branching seems more sensible move to make, but > we must make sure that users downloading package xyz.tar.gz know that it > will not work with php4, maybe somthing in the installer sould chack a > compatibility tag in the package.xml file saying > > <compatible>5.0</compatible> What does this mean? That the package is compatible with PHP 5.0 only? What about 5.1? :-) > then during installation the installer will check the running php version > and instruct the user that this package will not work with the version of > php he has running, another idea to make this easier for users is to have a > check in PEAR.php for the version, somthing like pear::checkCompatibility() > and use it in all PHP5 only packages to warn the user. I don't think it's a good idea to add another layer of complexity to the installer. We have dependencies, which can be used to say that a package requires version n.n or higher of PHP. With the "state hack" I suggested in a previous mail (using "stable5" for PHP 5 releases, and "stable" for PHP 4 ones), it will be possible to seamlessly upgrade PHP 5-based PEAR installations. - Stig

Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc