[RFI] src/lib/inVM

[Brian T. Rice]

You've identified a current problem, but this is the wrong solution. I am 
working on a new module system to help users identify what's in the /image/, 
and manage basic dependencies.

One reason what you mention would not work is that the core/bootstrap image 
definition may change in the future, and indeed anyone can change it, not 
just us.

Paul Dufresne <dufrp at hotmail.com> said:

> Since there is no need (and even this can cause crashes) to load a library 
> that is
> already in the VM, I'd like to suggest to keep in src/lib only the library 
> not in the
> VM, and to create a new one called maybe src/lib/inVM for the one that are 
> already
> in the VM.
> 
> This would encourage people to load and try the one in src/lib (shorter to 
> type),
> and would encourage to use src/lib/inVM as a kind of code reference to look 
> at.