According to S11, there are three items that determine what gets loaded:
The distro builder would have this action. There's no reason why it should be separated.
I don't think so. For one thing, SourceForge is still CVS. Another is that some prefer svk over svn and (as I discoverd on feather) they're not identical.
This seems to indicate that Parrot is the thing we're installing modules for, not Perl6. So, we would have a module installer for each VM Perl6 targets? We have to reinstall eveyr time Parrot is upgraded? I'm not sure I like that ...
Maybe, instead, we should be looking at caching the bytecode from the module and it's used unless either Perl6 or Parrot or the module has changed? That would seem to be something for "use"/"require" to do ...
In reply to Re^2: Perl6 - Distribution builder/installer
by dragonchild
in thread Perl6 - Distribution builder/installer
by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |