Hi Anthony

Grog will probably know more about it

You certainly don't need to install all dependencies, just the one that are required to run the script(s)

MRL have a nice feature that it will install dependency that are not installed when need. The problem is that the dependency is not alway usable when it just get installed.

I usually don't install all dependency before running MRL. I just lauch my script and if it need dependency not installed, it will download them and I restart.

Not exactly what you want (user should not have to manually restart when a new dependency is need), but it's probably possible to create an "install script" that create the services need in your inMoov script. That will download the dependency needed (instead of all dependency) and save a bit of time and bandwith

just an idea

There is a whole service dedicated to manage, restart, start new instances ....
Its called the "Agent"

Its purpose it to manage MRL instances, just as Runtime manages MRL services .
Everyone uses it, but they don't realize they do.

Whenever you start MRL your actually starting the Agent, and the Agent starts the MRL you use.

Take a look at processes explorer when myrobotlab.jar starts ..  it shows 2 processes.
The first one is the Agent's process .. started with "java -jar myrobotlab.jar"
It started the "real" myrobotlab instance - the one everyone uses, it contains all the necessary JNI & JNA command line entries, and default services to start.

How do you get to this service ?

MRL has its own command line interpreter.   I like using it.  
At the command line type "ls"
You'll see it list the current running services ..

You can inspect each service with the cli 
It has the same api as the webgui.
If I want to see the data of the runtime i can do this

ls /runtime

or look at the methods I can do this

ls /runtime/

or if i want to call a method I can do this

/runtime/start/arduino/Arduino

Pretty cool no ? 

But now to get back to the Agent ...  how do you get to the Agent from the command line ?  Its in a totally different process ! 

No matter, all you have to do is "detach" from the current myrobotlab process

detach

now when I ls I see the Agent's services in its process (I've moved from process to process)

The Agent can control many local instances of MRL.
It can start them, stop them, upgrade them etc...

To look at the processes the Agent is currently controlling do this

/agent/lp

lp is "list processes"

Here you can see I'm running 1 locally built mrl process - with process id 0

I could kill it - with 

/agent/kill/0

but lets not do that, instead lets start a UI

To show a UI I just start the admin webgui.

/agent/startWebGui

Grrr .. looks like the GUI's borked

Anyway - you "previously" could manage multiple mrl instances - with kill, shutdown & auto-update

Heh, 
Here is a previous post where it looks like your asking the same question ;)

http://myrobotlab.org/content/agent-or-how-mrl-starts