Re: Re: dependencies and applications

Hi, Alan Knowles wrote:

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.

how about adding an option to the installer to install dependancies into a subdirectory of the application directory..(htdoc/publicweb)? <dep type="pkg" rel="eq" version="1.3" target="publicweb">DB</dep>

This seems really promising. I'm not sure I follow the htdocs/publicweb connection, here's what I think you're saying :) PhpDocumentor's role="php" files are installed in PhpDocumentor/ if I have a <dep type="pkg" rel="eq" version="1.3" target="treemenu">HTML_TreeMenu</dep>, then HTML_TreeMenu would be located at PhpDocumentor/treemenu/HTML/TreeMenu.php. Any publicweb/htdocs files would be located at /path/to/publicweb/PhpDocumentor/treemenu/HTML/TreeMenu/, any data files at /path/to/datafiles/PhpDocumentor/treemenu/HTML_TreeMenu, etc. This still requires a change to include_path in the application, but it should work as long as applications know this (documentation will fix that). That gives me another idea of a way to handle this. it could still be installed in MDB/1.0/, and include_path set to look in this directory before the global directory, which would allow applications to share instances of the latest 1.x branch, and share bugfixes. Regards, Greg