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.
  • Earlier today on the IRC channel, Will Coleda made an interesting comment regarding partcl.

    07:28 <@Coke> I'd rather have folks go to /partcl/ to get parrot.

    That makes a lot of sense. So, have you given much thought to how you want to enforce and/or manage the version of Parrot you will be running Rakudo under? I think this may be an important issue. Given how much breakage we see in languages still in the parrot repository, I worry that decoupling of parrot from rakudo will only make the "moving target" problem worse.

    Presumably, Rakudo itself is in the best position to define which version(s) of Parrot it expects to run under. So do you think there should be some kind of startup sanity check? Or going even farther, a "make parrot" target which (if the appropriate version of parrot isn't found on the system) goes and fetches it, unpacks and builds it?

    • I've just posted a reply to this comment on the perl6-compilers mailing list -- when perl6.org's mailing list manager catches up it should appear here [google.com].

      (It seemed more useful to put it on the mailing list than to try to keep separate threads on use.perl, rakudo.org, and the mailing list.)

      Pm