in reply to Test::Prereq difficulties

You should be able to track prerequisites without a module, but if you can't, just grab a copy of Module::ScanDeps and use it to generate a list.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re^2: Test::Prereq difficulties
by brian_d_foy (Abbot) on Mar 04, 2005 at 13:21 UTC

    There are a lot of things we should be able to do without a module, but that's not reality. Modules like Test::Prereq, Test::Pod, Test::Distribution, and so on help us figure out what we forgot to do.

    You might be able to track prerequisites without a module, but that tasks gets harder when it's more than a couple people working on the code or the code base gets larger. There's no reason to tell someone that they shouldn't use a computer to check their work. :)

    Module::ScanDeps is okay, but it's better to actually run the code and see what it uses rather than parse the code and guess.

    --
    brian d foy <bdfoy@cpan.org>
      There's no reason to tell someone that they shouldn't use a computer to check their work. :)
      It's a good thing I didn't suggest that then ;)
      Module::ScanDeps is okay, but it's better to actually run the code and see what it uses rather than parse the code and guess.
      Sure, but Test::Prereq is overkill.

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.