Re: Re: Question wrt dual-PEAR

MadCoder wrote: > I'll go in the sources of PEAR package manager and try to see if a sth > clean can be make about that problem. Ok, here we are ... the *main* problem (against the feature I want) is the PEAR_Config class. it is designed to take a local *and* a global conf. but the local settings *override* globals. they do not complete them. So it's a dead end. I've looked at the sources, and incorporate the feature I would like to have (as a debian admin and a debian packager) would mean quite a big design refactor (at least in PEAR 1.3.x). *BUT* I have some kind of idea of a hack, but that *may* be a quick and dirty solution : we may build /usr/local/share/php/.registry/ have a lot of symlinks to /usr/share/php/.registry/*reg files I've tested, at least the installer works correctly. The problem is wrt packages you may want to upgrade. e.g. debian ships atm PEAR 1.3.2. maybe the root wants to have 1.3.4 ... if he does : pear upgrade pear then it will overwrite debian's pear 1.3.2 and not : delete the symlink in /usr/share/local/php/.registry and do a pear install pear. And I believe it will be rather hard to write a wrapper smart enough to avoid such problems. Does anybody has ever tried to maintain such a dual PEAR tree ? -- ·O· Pierre Habouzit ··O OOO http://www.madism.org