Re: Re: Question wrt dual-PEAR

Pierre Habouzit wrote:

Greg Beaver wrote:

You should also look at how gentoo does its ebuilds for pear packages. The --nodeps option is your friend. All you need to do is tell PEAR to ignore all dependencies in package.xml, and make damn sure that dpkg handles them properly (pear makedebian would do this part), and then you can avoid the problem.

well, I do not like it fully since it will lower a double check, that could be quite nice. but maybe it's the only solution. I'll follow your advice and look at gentoo's way (even if it can only be evil ;P)

Know thy enemy. ;) Gentoo does not assert the control over packages that debian does, so things would obviously need to be different, but they did find an incredibly simple way to do ebuilds that uses the pear installer directly.

my only concern was with the fact that even with this set like this, is what we talked a lot about : dependencies, local tree won't benefit of the debian one. :/

This is not such a big deal. Users who are installing packages would get simple error messages instructing them to install package blahblah, and then do it. You could also mention in the docs the --onlyreqdeps and --alldeps tags, which automatically download and install all dependencies, the first only required, and the second required and optional deps. Greg