what about putting RBengine in pharo1.2 core?

I wouldn't pre-load it. There is really no point for many deployed
applications to have it in there.

Lukas

On 27 August 2010 13:33, Stéphane Ducasse <[hidden email]> wrote:
> marcus like that we do not have to load it all the time.
> I could esaily update scriptloader to make sure that we do not save these packages.
>
> Stef
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

sure

this is just that during the unstable phase we need better tools. We want to run SmallLint.
The problem is that generate a new image every 20 min when I integrate and I do not want to spend my time load ob and rb.

After we will unload it.
And yes I should work on a configuration of pharo and rebuild the scriptloader infrastructure on it :(

Stef

On Aug 27, 2010, at 1:41 PM, Lukas Renggli wrote:

> I wouldn't pre-load it. There is really no point for many deployed
> applications to have it in there.
>
> Lukas
>
> On 27 August 2010 13:33, Stéphane Ducasse <[hidden email]> wrote:
>> marcus like that we do not have to load it all the time.
>> I could esaily update scriptloader to make sure that we do not save these packages.
>>
>> Stef
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project