Re: Question wrt dual-PEAR

Ian Eure wrote: > I think that what's needed is something like dh-make-perl for PEAR; > dh-make-pear. > > PEAR packages get handled in Debian in the usual way (ITP'd, uploaded > etc), but if a user wants to install an unpackaged or newer version of > something, they have to use dh-make-pear to create a Debian package first. > This sidesteps the whole issue of having two PEAR installations and the > mess that it brings. the thing is, you can install your own perl package with the usual make Makefile.PL or whatever the method is or run : cpan> install foo (or whathever the command is) without breaking anything. and even if it's a stupid idea, a lot of users do such a thing, and debian supports it. >> AFAIK it's the way perl is handled in debian (and in many linux distros) >> and it works quite fine ! >> > You seem to have made up your mind already. Why bother asking if that's > the case? I cannot understant your answer ... sure I made my mind about how I would like to see pear packaged for debian ... in fact the debian policy [1] made up my mind. and the perl, pyton, emacs and so on ... packages have made up my mind. It's allways a good idea to use similiar concepts to package simliar things. And I don't want to offend you, but perl, python are quite similar to php (wrt to their common uses). but oddly it's not handled the same way. And I know that php packagers do not like it, but they don't have the time to fix it. (I talk with them multiple time on IRC, deploring the debian state for PEAR packages). I want to make things evolve, and I may need some tiny support from you PEAR guys. I think we want both to find a good solution : * you don't want to rewrite PEAR for debian (and that's normal) * I cannot/have not found any solution to install PEAR the good way (TM) so maybe without rewriting all PEAR you can only add an option to pear that tells him how to look for dependencies in multiple directories. it's in fact all I need. -- ·O· Pierre Habouzit ··O OOO http://www.madism.org