Library system (aka ballpit)

[PaulBone]

Once bytecode is linked into libraries we need a way to manage those libraries, both locally (user directory and system wide) and as some kind of repository. My notes so far;

• Balls shall be the packages you get from a respository.
• The repository is the ball pit.
• Balls contain:
  • Bytecode
  • Interface data
  • (optional) optimisation interface data
  • Other code, like C code, .so files,
  • Documentation (mutliple formats)
  • Other data / examples / icons
  • For reproducable builds (likely as a link to a git/other repo with a
    tag):
    • Source code
    • Source docs
  • Meta-information.
• Not everything is always installed/used. Eg one may only install
  bytecode if it's not in a development context, or use that to build
  native code then discard it.

Blocked on #50 and #249