I think it should follow unix standard here..
$phpdir/pear/MDB.1.0.php
$phpdir/pear/MDB.2.0.php
where
$phpdir/pear/MDB.php is softlinked to $phpdir/pear/MDB.2.0.php
OK - this wont work..!! -
If you distribute applications that use specific versions of pear, then you have to use the include path to override the defaul packages.., and use them from your specified target....
(basically install them in you webdir/ or a packages subdir, and use
set_include_path(dirname(__FILE__).'/pear_fixed_versions',get_include_path());
I think modifying the current naming/layout structure would meet considerable resistance, especially when you can fix it in other ways...
Regards
Alan
on windows you will have to copy the latest one into place....as it doesnt have softlinks...
one of the beauties about pear at present is the direct mapping of classname=>include path.. - which makes locating code alot simpler...
I would also suggest making this as a configuratable option., as it's a bit of an overhead.. for alot of installations.
I missed though why you could not just point php_dir at another folder, then call the installer internally to install all the packages in order...
Regards
Alan
This is better.
I really like this idea, and it would work beautifully for dependencies. Definitely a PEAR 2.0 must.
Greg
I really feel that if we're going to do this, we should either get 2.0 out really soon, or do it in 1.x (bad). Otherwise there will be too many scripts relying on the current path system and a change to this is going to be met with too much resistance.
- Davey