Re: dependencies and applications

Zitat von Alexander Merz <alexander.merz@web.de>: > 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 > > An use case: > you install the current DB (ie. v1.3): > pear-lib install DB > > The you install an application, ie myDBAdmin > pear-app install myDBAdmin > > pear-app checks the deps of myDBAdmin, and find such thing like "require > DB 1.x". It checks with pear-lib if this version is installed; and > it registers in the pear-lib registry, that an application requires an > 1.x version. > > two months later: > you update DB to 2.0 > pear-lib upgrade DB > pear-lib see, that this a new major version and checks its registry, if > there are any dependencies of apps requirering a lower major version. If > this is true, it copies the current installed 1.3 version to the base > dir of the applications. This sounds interesting, but how to handle the include_path issues? The include path should be set to pear-lib's repository. That means that pear-app-installed application will use: include 'DB.php' We made the experience that relative include paths sometimes don't work thus simply copying DB.php and the other files to the application's directory won't be enough, even if "." is in the include path. > 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! Jan. -- http://www.horde.org - The Horde Project http://www.ammma.de - discover your knowledge http://www.tip4all.de - Deine private Tippgemeinschaft