A few thoughts for consideration.

• All files relating to a particular module(version/author) should exists in a directory tree below that module's place within the file system. Including, but not limited to:
  1. Distribution files (.tar.gz etc.)
  2. Build files (makefiles, source files)
  3. Built files including binary (dynamically linked) components.
  4. Test files.
  5. Build process log files.

  One exception might be generated docs like htmlized POD/man pages.

• Parrot can save/load bytecode files.

  At use time, the first thing looked for should be a pre-compiled Parrot bytecode file. If found, this can be loaded, bypassing the need for compilation. Some check for updates should be possible.

  When a module is installed and tested, the bytecode is written out to the appropriate place (if tests pass?) and that module need never be recompiled until a new version is downloaded.

• If I've been following things correctly, Parrot bytecode is platform independant?

  If so, it would sometimes be convenient to be able to download the bytecode only from CP6AN. Even better if this could be done (safetly) on the fly.

• As well as use implicitly loading the latest version of module where the version is unspecified, and the specified version when requested, the ability to hold debug and/or development versions within the same libtree and request they be loaded would be handy.
• A tool for taking a development version directly from the libtree and packaging it for distribution would be a nice convenience.
• An tool equivalent to Module::Starter that created a development skeleton in-situ would complete the toolset.
• Random thought. I wonder if there is any scope/merit in adding svn source control into the mix?