Re: PEAR and PHP 5

On Thu, 2003-04-10 at 06:17, George Schlossnagle wrote: > On Wednesday, April 9, 2003, at 08:56 PM, Stig S. Bakken wrote: > > > > This is a good point. So translation should be done during upload > > instead. > > Forgive me if I've missed something about how PEAR works, but it seems > quite hard to change an uploaded version once it's been uploaded. > Perhaps this should be done by the packager-cli so that the author can > verify consistency before the upload? Each release may have several files associated. Today there is only one, but if/when we start distributing binary builds of PECL packages there will obviously be several. This could be done with the same approach. When you upload a PHP 4 package, the original, unmodified PHP 4 version is stored in one .tgz file, and a PHP 5 version with translated code in another. Which file you actually get when requesting "Foo-1.0.tgz" is determined by the "get" script on pear.php.net. If your installer says it's installing for PHP 5, it will be given the Foo-1.0.php5.tgz tarball instead. It could be done by the packager, but that gives us a much higher bugfix/new-feature latency for the code translation, since everyone have to upgrade the installer. Could cause a chicken-and-egg situation if we're not very careful. Doing it on the server means a single place to upgrade and re-formatting any packages that may have been bad. - Stig