Re: Re: Question wrt dual-PEAR

Ian Eure wrote: >> Seriously though, the way PEAR works is there is a system configuration >> file and a user configuration file.  If you want two installations of >> PEAR, the PEAR way is to have 2 configuration files, one for each >> installation.  In this way, the PEAR installer elegantly allows install >> of local copies of a package. >> > I've never tried this type of setup. Are dependencies from the system > installation considered when installing something into the user's > installation? that would be great. though, I cannot write anything in ~root for many many many very good reasons. In fact, what I seek would be that /etc/pearrc (if that can exists) says that default installs is in /usr/share/local/php and only when dpkg uses pear to install modules then it overrides it (if possible on the pear command line) in order to install it un /usr/share/php My big problem was that I don't want to break dpkg -l foo (this command lists the files in a package) and for that, I need to know at packaging time which files will be installed (and the new pear postinst feature make me fear my kludge will not work anymore [1]) >> The debian package manager could easily wrap the pear command, as Alan >> Knowles suggests, and pass in a hard-coded user config file if it isn't >> specified on the command-line. >> >> In other words, the pear script would be called with >> >> pear -c /path/to/debian_usr_local_share/pear.conf $@ >> > Unless you're talking about just packing up a PEAR .tgz file and calling > the pear install command from the postinst script, this will never happen. > Dpkg is a critical part of the Debian system, and there's no way a change > to support one supplier's idea of What's Right(tm) would get accepted. this can happen, but with sth more kludgy as I said. I use the ability of pear to be able to register a library without installing it (again see [1]) [1] : http://www.madism.org/debian.pear.php -- ·O· Pierre Habouzit ··O OOO http://www.madism.org