Re: Re: dependencies and applications

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

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

This is a user-level solution - one which require a considerable amount of work as well as expertise from the user, as well as customization of an application. This certainly does not compare to the old-fashioned ease of simply unzipping an application with all of the dependencies bundled - and the only advantage PEAR currently holds will be if it makes it easier to install an application with dependencies. If there are other ways to fix it that really do fix it, I think they should be seriously considered, but I don't think requiring the user to do any unnecessary work will solve this problem. Greg