Re: dependencies and applications

Alexander Merz wrote:

Greg Beaver wrote: There is a simple solution (from a users point of view) We split up the command pear into two different: "pear-lib" for library packages "pear-app" for applications

[snip]

This keeps BC behavoir keeps BC at all and solves the publicweb problem, because a pear-app must support installing on every directory, not only to the PEAR-Dir!

I agree this will work for applications, but I don't think it solves the publicweb problem, because a user application (not a re-distributable one) that relies on HTML_TreeMenu, for example, will still have to do a bit of an install dance to get access to the images and javascript. They will first attempt to use the HTML_TreeMenu out of the box, which won't work because the images are not found - but no error message is displayed, so they will end up thinking "well, this doesn't work at all" and abandon it, unless they know to look in the data directory, which is probably hidden away as a subdirectory of the pear/ directory buried in the /usr hierarchy... :) Greg