On Fri, 2008-09-05 at 11:15 -0700, Russ Allbery wrote: > Niko Tyni <[EMAIL PROTECTED]> writes: > > > The implementation could use corelist(1) and/or Module::Corelist to > > check if the version in the dependency is already in the core. I think > > just transforming libfoo-bar-perl to Foo::Bar would catch most issues, > > and the rest (like podlators-perl -> Pod::Man) could be special cased. > > One trick here will be that lintian.d.o runs on a stable system and hence > would have stable versions of those utilities unless we add newer versions > to a private library directory. We can do that, of course, but it may be > worth considering whether we should generate some sort of static dump of > the data and update it periodically instead. I'm not sure off-hand which > would be easier to maintain, or if there's some other, better way.
How often do new (packaged) modules get merged in to the core? On the assumption that it's not a hugely regular occurrence, I'd be minded to suggest maintaining a static copy, as we do with the doc-base section list. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
