On 8/23/06, stéphane ducasse <ducasse at iam.unibe.ch> wrote:
> let us talk about a scenario.

script A has such and such dependancies
script B has some others
...

Do I prepare a big runtime-environment-image with every dependency
needed for scripts to come?
I might like the image persistency for a given script, but if I have
only one image for all scripts this will eventually break. One image
per script duplicates too much (how to keep all dependancies
up-to-date in all images?).
So each script has an environment that should be rebooted from time to
time, but also some private persistent data (spoon imprinting and
instant loading ?)

-- 
 Damien Pollet
 type less, do more