On Fri, 12 Nov 2010 23:21:02 +0200, Damyan Ivanov wrote:
> > For lib.*-perl package it might be a bit annoying having to find out
> > in which of the packages a dependency is.
> You mean, because not every module is in separate package? Hm, this
> can become tricky.
Yup.
> META says Foo::Bar 1.3 is needed, how do we tell if it is in
> perl-modules x.y or in libfoo-bar-perl 1.3?
That's already the status quo, and apt-file, dh-make-perl plus
corelist -a help. But if we get more than perl and perl-modules it
might get complicated. - If it's "just" separate one-package-per-dist
packages (lib.*-perl) then it's fine.
> Module::CoreList::Debian?
Something like that would be nice, for the modules provided by
perl/perl-modules and created by the perl source package.
That might also make it possible to make dh_perl more knowledgable,
as Martin suggested. (Although ${perl:Depends} doesn't help for
build dependencies.)
> > (Unless we can still use a
> > dependency on a main "perl" package that pulls in all of its
> > siblings and the rest is an internal implementation detail of the
> > perl source package.)
> Except that this would defeat the point of splitting modules off
> 'perl-modules'
Right :)
Cheers,
gregor
--
.''`. http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
: :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe
`- NP: Rolling Stones: Midnight Rambler - Wembley 10-09-73
Attachment:
signature.asc
Description: Digital signature