Re: Re: dependencies and applications

I think a bigger issue with MDB.1.0.php is what if that files uses /MDB/Common/etc.php and so does MDB.2.0.php suddenly you have a conflict. If you're going to allow for the installation of different versions in different places they need to be isolated in a directory like earlier mentioned. Granted I may not be understanding this, and if so I apologize. - Stan Alan Knowles wrote:

Davey wrote:

Greg Beaver wrote:

Lastly, we need to think about having some sort of "slot" system such

as they have in Gentoo for their ports, whereby you can install more than one major version of an application. This will mean some changes to the folder structure, and if it happens should be done ASAP so that we can just get the change over and done with IMO. I suggest something along the lines of: $php_dir/pear/MDB/1.0/MDB.php and $php_dir/pear/MDB/2.0/MDB.php

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 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