Hi!
On Mon, Jul 20, 2009 at 11:47:44AM +0300, Damyan Ivanov wrote:
> -=| Ryan Niebur, Mon, Jul 20, 2009 at 12:17:46AM -0700 |=-
> > On Mon, Jul 20, 2009 at 10:00:41AM +0300, Damyan Ivanov wrote:
> > >
> > > I think the right fix would be in Module::CoreList. Luckily we
> > > maintain libmodule-corelist-perl and dh-make-perl already depends on
> > > it. A fix may be propagated upstream in the next point release (and
> > > end up in perl-modules).
> > >
> > > I assume (and this worked so far) that each module in
> > > /usr/{share,lib}/perl/$version is a core one. If this not true, then
> > > we just can't do anything but trust Module::CoreList and t/corelist.t
> > > shall be rewritten to simply check a couple of modules we know are
> > > core ones instead of going over the directories.
> > >
> > > I somehow that Module::CoreList is wrong here, so this better be fixed
> > > there upstream (and patched in libmodule-correlist-perl until upstream
> > > releases a fixed dist).
> >
> > I think this "module" is Debian (or admin) specific tho and not a real
> > module, since it's for configuration. so it seems very wrong for
> > Module::CoreList to list this.
>
> OK. What I try to avoid is keeping a list of exceptions. This will
> break the next time such a module appears.
> true. > I was thinking if we can exclude all modules found under /etc/perl? Or but it's not under /etc/perl. > is there a non-zero change for "true core" modules to appear there? > what do you mean by this? -- _________________________ Ryan Niebur ryanrya...@gmail.com
signature.asc
Description: Digital signature
