Re: real-world example of (smart) developers using PEAR without installation

Hi list, I haven't been reading the PEAR list for too long, but since I was part of the discussion Greg linked to, I'd like to say a few words. When I deploy applications that depend on PEAR libraries, I put them in a subdirectory of the application, because I want my application to be self-contained and not rely on centrally managed PEAR packages on the target server. This works when . is in PHP's include_path before the PEAR directory, which should be the case. If not, I can modify the include_path setting in my application startup file. The use case Dirk described in the discussion Greg linked to is more complex, though: he wants to have all tools he uses for a project under version control, so that he can basically check out a full working environment from Subversion. This seems a good idea when you do many project that work with a different toolset over time. The question is how well this approach works right now when applications like phing put XSL stylesheets into the PEAR data directory. As accessing the PEAR data directory is not based on include_path, does the application find it or will it just go looking in the data directory of the existing PEAR installation. And what would happen if no local PEAR installation exists at all? Kind regards, Stefan -- >e-novative> - We make IT work for you. e-novative GmbH - HR: Amtsgericht München HRB 139407 Sitz: Wolfratshausen - GF: Dipl. Inform. Stefan Priebsch http://www.e-novative.de