Re: Re: Channels

On Sat, 19 Jun 2004 08:47:48 +0800 alan@akbkhome.com (Alan Knowles) wrote: > > >Are you talking about having the same tree for many (major) php > >versions? > > > > > well in 10 years, phasing out PHP4 code may be realisitic.. I > would prehaps consider it more like debian sources, stable (PHP4), > unstable (PHP5) - I'm not talking from our side but from the userside. An user can setup two distinct trees, one for php4 and one for php5. Setting correclty the preferences of each. > >Do we have to support every upcoming php releases? Or are you > >thinking about some realtime dependencies? Like I cannot load or > >run a php5 script using a php4 install? > This may be a reality at a 5 year release cycle, this may not be a > big issue. PHP5, if used properly, really looks like another > language, trying to kludge it into a PHP4 box may prove futile in > the long run. > >Then they do not install php5 packages. They cannot even do it > >using the normal way (only with --force, for now). > > > > > That doesnt stop my system getting in a mess if I install PHP5, > install a few packages then downgrade to PHP4 if things dont work > out..) - yes I know doing things sensibly, would prevent issues, > but how many end users do you think would make a mess.... > > if .php5 & .php4 are not going to be to popular (although I think > it makes the distinction alot clearer), perhaps /usr/lib/pear5 > (default folder for a PHP5 channel) Still failed to see where a PHP5 is usefull, just setup a new tree with the right settings could be the way. Imagine 2 channels defined on the client side, but each of them has different settings (dep php>5 or <=4.x) and both points to the "normal" PEAR channel. --Pierre