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.
  • This is very, very shiny. Thank you.

    How are you planning to deal with the fact that different repositories have different semantics for describing dependencies? (For example, not all CPAN modules make the distinction between dependencies needed at install time and runtime).

    What assumptions are you making about a CPAN module distribution? (I started an effort to try to document exactly how a distribution was made up, but had to leave it for other things a few months ago, looks like I should start working on it again.)

    What assumptions are you making about a module's build system?

    How are you planning to deal with module tests?

    Do you have a website/mailing list/hive mind where you're coordinating all of this?
    • > How are you planning to deal with the fact that different repositories
      > have different semantics for describing dependencies? (For example, not
      > all CPAN modules make the distinction between dependencies needed at
      > install time and runtime).

      Some of this is still unsolved.

      Currently I think there will probably be built-in vocabulary for dependencies that covers 5 phases (config, build, test, install, runtime) and some concept of a resource with various subtypes (packages/distribution, class/inte