Re: Re: dependencies and applications
| From: | Alan Knowles | Date: | Thu, 21 Aug 2003 02:14:24 +0000 |
| Subject: | Re: Re: dependencies and applications | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20204@lists.php.net to get a copy of this message | ||
Davey wrote:
Greg Beaver wrote: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 AlanLastly, we need to think about having some sort of "slot" system suchas 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 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. - DaveyThis is better. I really like this idea, and it would work beautifully for dependencies. Definitely a PEAR 2.0 must. Greg