use Perl

• Proper dependency specification (Score:2)

  by rafael (2125)

  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
• Use the CPAN Luke (Score:2)

  by barbie (2653)

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

  • Acme::Prereq::A [cpan.org]
  • Acme::Prereq::B [cpan.org]
  • Re:Use the CPAN Luke (Score:1)

    by cog (4665)

    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.
• use CPANPLUS instead then :) (Score:1)

  by kane (2600)

  It actually does the right thing when detecting recursive dependencies... try it out ;)
  • Re:use CPANPLUS instead then :) (Score:1)

    by cog (4665)

    True, but what would happen to the CPAN shell users? :-)