I say list them all, but we should encourage tools to make that easier/automatic. It could be done at "make dist" time just like the rest of META.yml unless the author overrides it.
Personally, I have a script which searches for modules and prints them in the right format, plus adds either the current version on my build machine or a "pinned" version for certain modules. It also adds a comment with the Module::Corelist results so I can see what versions were in core at different major points for dual life modules. David On Fri, Apr 11, 2008 at 7:04 AM, Gabor Szabo <[EMAIL PROTECTED]> wrote: > Hi, > > we have been discussing with Domm how CPANTS should check if a > distribution declares each of its prerequisites correctly which brought > us to the the point that we have a problem. > Let's focus for now only on dependencies on other CPAN modules and > not on external libraries. > > So if I am using Tk::Widget::A and Tk::Widget::B... Tk::Widget::Z all > provided by Tk. > Should I add all of them as prerequisite of my module or should I add only > Tk? > > The former is lots of work on my side but I think that is the more > correct way to do it. > If I only require Tk then one day Tk might be split in two distros Tk > and Tk::Extra, > moving some of the widgets to the extra distro. This will break my > modules dependency > declaration. > > What do you think? > > I have started to outline the recommended way of doing this here: > http://www.perlfoundation.org/perl5/index.cgi?cpan_packaging > but of course your input is highly appreciated. > > regards > Gabor >
