On Wednesday, March 6, 2002, at 11:48 AM, Stas Bekman wrote: > The real problems with prerequisites are: > > - some modules don't specify prerequisites :( But I think we can add > code to parse the code to figure out simple require and use cases. > Weren't there a module doing this? I think I read about it in some old > TPJ. Anyone?
I wouldn't do that if I were you. Too much room for error and annoyance. If a module doesn't specify prereqs, there's not much we can do, unless you want to maintain a manual list of unspecified prereqs. > - should you bundle only prerequisites which aren't installed on the > system the bundler runs on, or should it take all the prerequisites. I > guess this could be an option. That would be a nice option. > - what happens if a certain version of perl is a prerequisite? Should > it be grabbed too? But then it's not perl Makefile.PL && make install. > This could be a big problem. It should probably just be noted as a prereq, and then if you attempt to install on a machine that doesn't have the right perl version, it should fail. Presumably it'll fail somewhere in one of the module installations anyway. > > Good idea. If nobody comes up with another name, it'll be CPAN::Bundler > I don't like that much, because it doesn't actually create a CPAN Bundle (does it?). -Ken
