[Replying to list with submitter's permission, therefor full quote] On Wed, Jan 25, 2006 at 10:40:46PM +0100, Florian Ragwitz wrote: > I'm a Debian developer who cares a lot about Perl packages in Debian. > Therefor I know pretty well that many other developers suffer from the > lack of a program like dh_shlibdeps for perl programs and modules. I > want to change that. > > There were already some bugreports against debhelper that asked for a > new dh_ script that handles the dependency analysis for perl modules. It > has been tagged wontfix as the maintainer and author of debhelper thinks > that debhelper is not the right place to do a complex such complex > things like dependency analysis. He recommended that I should go the > "dpkg-shlibdeps" way which does the analysis of dependencies with an own > script which is then glued into debhelper with a small wrapper script. > > This is what I want to do with dpkg-perllibdeps (the name is still > object to change). I'm writing you to ask if this program could be > included with the dpkg-dev package, what I would prefer over making it a > seperate package. I'd like to use libmodule-scandeps-perl to do most of > the work. This would introduce a dependency for dpkg-dev to this > package. I don't know if that is tolerable for you. If not: how about > shipping an own copy of Module::ScanDeps so it can be included into > dpkg-dev. This has some disadvantages, obviously, but I don't like the > idea of making dpkg-perllibdeps a seperate package. > > What are your thoughts?
What do the others think about introducing more dependencies for dpkg-dev? Since it is build-essential we should certainly not introduce new dependencies too lightly but on the other hand using some external perl modules can lighten the code maintainance burden... Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
