Bug #42949 for CPANPLUS-Dist-Deb: use dpg -S and apt-file to determine dependencies

Sun Feb 01 10:49:30 2009 martijn [...] cpan.org - Ticket created

Sun Feb 01 10:58:32 2009 martijn [...] cpan.org - Severity Wishlist added

Sun Feb 01 10:58:32 2009 martijn [...] cpan.org - Correspondence added

(meh, quick-create is useless) wouldn't it be an idea to first try to find out which package in debian has a certain module by using `dpkg -S "Some/Module.pm"` (or `apt-file search "Some/Module.pm"` if it isn't installed) ? That way you wouldn't need to have an enormous ignore/ban list to get some modules to install.

Sun Feb 01 10:58:33 2009 martijn [...] cpan.org - Subject changed from (no value) to 'use dpg -S and apt-file to determine dependencies'

Fri Jun 12 16:48:52 2009 hdp [...] cpan.org - Correspondence added

On Sun Feb 01 10:58:32 2009, MARTIJN wrote: Show quoted text

> wouldn't it be an idea to first try to find out which package in debian > has a certain module by using `dpkg -S "Some/Module.pm"` (or `apt-file > search "Some/Module.pm"` if it isn't installed) ? That way you wouldn't > need to have an enormous ignore/ban list to get some modules to install.

Can you be more specific about this "enormous ignore/ban list", and which modules you find yourself using it for? I can't imagine you mean the defaults, which are fairly small.

Fri Jun 12 16:48:53 2009 The RT System itself - Status changed from 'new' to 'open'

Sat Jun 13 06:22:34 2009 martijn [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #42949] use dpg -S and apt-file to determine dependencies
Date:	Sat, 13 Jun 2009 12:22:14 +0200
To:	bug-CPANPLUS-Dist-Deb [...] rt.cpan.org
From:	Martijn van Beers <MARTIJN [...] cpan.org>

On Fri, 2009-06-12 at 16:48 -0400, Hans Dieter Pearcey via RT wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=42949 > > > On Sun Feb 01 10:58:32 2009, MARTIJN wrote:

> > wouldn't it be an idea to first try to find out which package in debian > > has a certain module by using `dpkg -S "Some/Module.pm"` (or `apt-file > > search "Some/Module.pm"` if it isn't installed) ? That way you wouldn't > > need to have an enormous ignore/ban list to get some modules to install.

> > Can you be more specific about this "enormous ignore/ban list", and > which modules you find yourself using it for? I can't imagine you mean > the defaults, which are fairly small.

I haven't kept a list unfortunately, but there's surprisingly many modules that debian breaks the libmodule-namespace-perl convention for, and there's a lot of modules in the core (so package perl-modules). Anytime one of those is listed as a dependency, the .deb builds fine, but has faulty dependencies, which makes dpkg complain. Trying to add to the ban/ignore lists would result in an 'arms race', which is why I suggested trying to be smarter about what debian package provides a perl dependency.