Thanks. I'll know where to look next time. :\

I think I'm missing something. That link shows how to specify which version to include, but I don't see where it specifies how they are stored. Specificaly it says "Modules posted to CPAN or entered into any standard Perl 6 library are required to declare their full name so that installations can know where to keep them, such that multiple versions by different authors can coexist, all of them available to any installed version of Perl." Any ideas if that has been decided yet? /me considers overloading use to pull modules out of a database just for kicks. ;)

If you load 2 modules that try to load different versions of the same module, the result can be best described as "interesting". Sometimes it will work, but I wouldn't want to trust it. If that module happens to be a binary module that loads a C-level library, your chances at even limited success drop drastically.

I firmly believe that a lot of work will go into making versioning work like the spec says, and then people will discover that trying to use the feature causes far more problems than it solves. Unfortunately they will only discover the problems after having committed themselves to the strategy for a while, and so will have created some nasty messes first.