So, you can have the C6PAN version and the debug version and it will "Just Work".

So, just make the debug version's author 'debug' or similar. Makes sense.

I don't think so. For one thing, SourceForge is still CVS. Another is that some prefer svk over svn

I guess I should have just said source control (omitting the 'svn'), but most everyone is seems to be settling upon svn recently. It would be kind of nice to have CP6AN be the master repository and then authors could just branch locally for the next version and commit to CP6AN when they're ready. Also, svn/svk will talk to each others repositories won't they? At least for the 'co' & 'up' commands?

And the download tool could use the intelligent diffing to update installed packages rather than downloading the whole thing. And just checkout new modules? Not sure if that could work, but the thought crossed my mind so I mention it.

I'm not sure where the sourceforge stuff comes in here? Is CP6AN likely to be on SF?

This seems to indicate that Parrot is the thing we're installing modules for, not Perl6.

I know that Parrot is intended to support multiple languages but I don't recall reading that Perl6 was intending to target multiple VMs?

In any case, when the builder runs the test suite, it could (optionally) issue a 

perl6 --cache-bytecode -MNew::Module

[download]

as a final action if the test passed. Or something...

I agree that it is probably a function of use/require to actually load the bytecode, but I thing the Perl6 executable could be asked to load/save/igonore cahced bytecode and the builder module could support thiose options on a case-by-case basis as well as it being a configurable option for an installation?

Anyway. Just thoughts for the pot.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.

In reply to Re^3: Perl6 - Distribution builder/installer by BrowserUk
in thread Perl6 - Distribution builder/installer by dragonchild

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.