Re: Re: cvs: pear /Net_URL URL.php package.xml

Helgi Þormar wrote:

Here's a idea I came up with on irc, and cox asked me to email it here so we can keep track of it. The idea is that we have 2x branches on each package if the lead wants to, so there would be one php4 branch and one php5 branch. And people could do pear install net_url then php4 version is downloaded and pear install net_url-php5 to download the php5 branch .... or even make it a config option what is downloaded by default if there are 2 branches present. So basically this would fix up the issue of making a new package for php5 only port of php4 package.

This suggestion creates tons of problems: 1) in the long run the API's are sure to diverge, even if just one gets additional features, which means you have to create a new major version at that point 2) just to get E_STRICT compliance I have a hard time seeing a valid enoudh reason to get into this support nightmare 3) even if you really really want E_STRICT then the "only" problem is that additional integer indicating the major version number which you have to type fairly seldom in most cases 4) it will bloat the installer and make the user experience more difficult

Note. this is not something that would solve the conflict of having php4 and php5 installation of a package, only so we don't have a major release of package just to get php5 only.

Well this is the least problematic point in this proposal, as even if you run php4 and php5 in parallel (which is not that feasible to begin with) then it shouldnt be a big deal to have separate pear paths in your include path for each. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07