Re: Re: RFC::Error Handling Guidelines for PHP5 packages

Stig S. Bakken wrote:

I agree, this is a very logical way of dealing with this when we have channels. The PEAR server can determine which packages should be included in each server by looking at type="php" dependencies: php4-only: <dep type="php" rel="lt" version="5" /> php4/php5: <!-- no dependency needed --> php5-only: <dep type="php" rel="ge" version="5.0" />

It wouldn't quite be this simple - the package would have to explicitly specify the pear5 channel in its package.xml as well. Fortunately, it's possible to stop any snafus at the packaging level using the channel-specific validator code. This would mean that the pear channel validator would not allow any php5-only packages to be packaged as a PEAR package, and the pear5 channel validator would not allow any php4-compatible packages to be packaged as a pear5 package. Also nice is that they PEAR channel validator could allow installation of php5-only packages to allow packages already released like DB_Sqlite_Tools to still be installed. Greg