excellent like that I can work on the loading part
I love sooo writing configurations.
Stef
On 20 Jan 2014, at 12:18, Pavel Krivanek wrote:
> Here is the job:
> https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKernel3.0-FromTopShrink/
>
> -- Pavel
>
>
> 2014/1/20 Sv
I made the script more general and easier to read:
https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKernel3.0-FromTopShrink/lastSuccessfulBuild/artifact/shrink.st
-- Pavel
2014/1/20 Pavel Krivanek
> Here is the job:
>
> https://ci.inria.fr/pharo-contribution/view/Pharo-Ker
Here is the job:
https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKernel3.0-FromTopShrink/
-- Pavel
2014/1/20 Sven Van Caekenberghe
>
> On 19 Jan 2014, at 09:44, Pavel Krivanek wrote:
>
> >
> > 2014/1/18 Sven Van Caekenberghe
> >
> > On 18 Jan 2014, at 20:53, Benjamin
>
On 19 Jan 2014, at 09:44, Pavel Krivanek wrote:
>
> 2014/1/18 Sven Van Caekenberghe
>
> On 18 Jan 2014, at 20:53, Benjamin
> wrote:
>
> > COOOLLL !!
>
> +1
>
> And interesting as well (I want to understand how to unload NB, for example).
>
> For simplicity I use the attached
Thank you very much Pavel!
I am eager to go smaller using the bootstrap process ;-)
#Luc
2014/1/19 Alexandre Bergel
> Impressive job!
>
> Alexandre
>
> Le 18-01-2014 à 16:37, Pavel Krivanek a écrit :
>
> Hi,
>
> I finally successfully created a script that is able to unload everything
> *by M
Impressive job!
Alexandre
> Le 18-01-2014 à 16:37, Pavel Krivanek a écrit :
>
> Hi,
>
> I finally successfully created a script that is able to unload everything *by
> Monticello* except kernel packages, network, Monticello, Gofer and related
> packages. I will setup a job when Jenkins will
On 19 Jan 2014, at 12:19, Stéphane Ducasse wrote:
> I guess that once we will use git it will go away. Does anybody know if this
> is a correct assmption?
yes, is correct :)
alll that information can live outside the image without actually lose of
information (it will be there, when we need i
wow. Impressive work, Pavel.
Thank you very very very much :)
this will be super useful for Pharo 4.
Esteban
On 18 Jan 2014, at 20:37, Pavel Krivanek wrote:
> Hi,
>
> I finally successfully created a script that is able to unload everything *by
> Monticello* except kernel packages, network,
I guess that once we will use git it will go away. Does anybody know if this is
a correct assmption?
On 19 Jan 2014, at 10:10, Marcus Denker wrote:
> Very very nice! I integrate issue 12679.
>
> Yes, Monticello meta data… we should check this issue:
>
>
> https://pharo.fogbugz.com/f/ca
On 19 Jan 2014, at 09:19, Pavel Krivanek wrote:
> Ben, can you take care of your child? ;-) I'm not against making UserManager
> part of the kernel packages, or better only Monticello prerequisity. But we
> need to separate the UI part.
Yes and the UI part is not stable. So we should remove
Very very nice! I integrate issue 12679.
Yes, Monticello meta data… we should check this issue:
https://pharo.fogbugz.com/f/cases/2711/Monticello-wastes-significant-amounts-of-memory
(but in general it is not good to have meta data of a versioning system in the
image… it needs to be on
2014/1/18 Sven Van Caekenberghe
>
> On 18 Jan 2014, at 20:53, Benjamin
> wrote:
>
> > COOOLLL !!
>
> +1
>
> And interesting as well (I want to understand how to unload NB, for
> example).
>
For simplicity I use the attached code. The image needs to be restarted
after NB unloading. T
2014/1/18 Stéphane Ducasse
> Excellent and impressive.
> Pavel did you publish it in SystemConfiguration?
>
some code is there but mainly because of backup purposes, it cannot work as
is.
> I would really like to see if we can add a unload protocol to the package
> manifest or configuration be
Ben, can you take care of your child? ;-) I'm not against making
UserManager part of the kernel packages, or better only Monticello
prerequisity. But we need to separate the UI part.
-- Pavel
2014/1/18 Benjamin
> COOOLLL !!
>
> Ben
>
> On 18 Jan 2014, at 16:37, Pavel Krivanek wrot
On 18 Jan 2014, at 20:53, Benjamin wrote:
> COOOLLL !!
+1
And interesting as well (I want to understand how to unload NB, for example).
> Ben
>
> On 18 Jan 2014, at 16:37, Pavel Krivanek wrote:
>
>> Hi,
>>
>> I finally successfully created a script that is able to unload every
Excellent and impressive.
Pavel did you publish it in SystemConfiguration?
I would really like to see if we can add a unload protocol to the package
manifest or configuration because it would be good to have
the knowlegde modular.
Stef
> Hi,
>
> I finally successfully created a script that is
FANTASTIC! We have another Pharo Hero!
Le 18/01/2014 20:37, Pavel Krivanek a écrit :
> I finally successfully created a script that is able to unload
> everything *by Monticello* except kernel packages, network, Monticello,
> Gofer and related
--
Dr. Geo http://drgeo.eu
This is beautiful!
Doru
On Sat, Jan 18, 2014 at 8:37 PM, Pavel Krivanek wrote:
> Hi,
>
> I finally successfully created a script that is able to unload everything
> *by Monticello* except kernel packages, network, Monticello, Gofer and
> related packages. I will setup a job when Jenkins will be
COOOLLL !!
Ben
On 18 Jan 2014, at 16:37, Pavel Krivanek wrote:
> Hi,
>
> I finally successfully created a script that is able to unload everything *by
> Monticello* except kernel packages, network, Monticello, Gofer and related
> packages. I will setup a job when Jenkins will be
Hi,
I finally successfully created a script that is able to unload everything
*by Monticello* except kernel packages, network, Monticello, Gofer and
related packages. I will setup a job when Jenkins will be healthy again.
It uses several temporary patches that we need to solve properly:
- make Nat
20 matches
Mail list logo
