Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The CPAN lacks proper dependency specifications.

    To do this properly, we probably need (1) to distinguish between pre-requirements and requirements. The first ones are necessary for installation, the second ones for usage (or for "make test"). And (2) transactional installations, that is, detect dependency cycles and install/upgrade sets of dependent packages as a whole. (Rolling back everything, of course, if one of the make-tests in the transaction fails.)

    That's what proper package management systems and

  • Whatever you think you need to try, nearly always someone has got there before you....

    • But I did use it... it's just that between the search I made and the day I finally decided to create the modules, those two showed up :-)

      Anyway, recursive dependency is only the first version of what I want to try, so my two modules (or at least one of them) will eventually see another version with another test. At some point, when I'm satisfied, I'll probably delete them.
  • It actually does the right thing when detecting recursive dependencies... try it out ;)