would be great.
I'm doing boring admin right now and I was trying to understand why I get a
problem unload Nautilus.
Stef
On Nov 27, 2013, at 1:46 PM, Pavel Krivanek pavel.kriva...@gmail.com wrote:
2013/11/26 Stéphane Ducasse stephane.duca...@inria.fr
On Nov 26, 2013, at 3:27 PM,
This is the list of newly created unimplemented calls:
Tests removal:
a SortedCollection('Array generateSpecFormat calls: s '
'FreeTypeFontProvider getWindowsFontFolderPath calls: char asPointerType
invokeWith:with:with:with:with: long
name:module:callType:returnType:argumentTypes: '
On Nov 26, 2013, at 3:27 PM, Pavel Krivanek pavel.kriva...@gmail.com wrote:
Hi Stef,
I started to play with this way of shrinking (see the attachment). At least
it's really faster than to use MC :-)
Sure :)
Do you have a ci job to produce an image systematically?
Where are the
Guillermo has several bootstrapped and minimal images.
I tried to find them but I could not
https://ci.inria.fr/pharo-contribution/job/Bootstrap/
Guillermo? Is now on holidays.
Yes, but coding when not seeing family :)
:)
https://ci.inria.fr/rmod/view/Oz/
OK I will try to
Hi Pavel, Hi All,
On Sun, Nov 24, 2013 at 10:11 PM, Pavel Krivanek
pavel.kriva...@gmail.comwrote:
Hi Stef,
our starting point looks like this:
- we have a method how to produce small image without network etc.
- we are able to load network, Monticello and Gofer in it (this job is
On Nov 25, 2013, at 7:11 AM, Pavel Krivanek pavel.kriva...@gmail.com wrote:
Hi Stef,
our starting point looks like this:
- we have a method how to produce small image without network etc.
- we are able to load network, Monticello and Gofer in it (this job is
currently broken)
- we are
From the practical point of view, it's always faster to remove. something
than to load something. And it's much faster to unload it without Monticello.
So I would use ugly removeAllButPackages: because it's fast, then fix the
problems like obsolete classes an Undeclared, continue with the
On Mon, Nov 25, 2013 at 5:09 PM, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
From the practical point of view, it's always faster to remove. something
than to load something. And it's much faster to unload it without
Monticello. So I would use ugly removeAllButPackages: because it's
Hi Guillermo, Hi Stef,
On Mon, Nov 25, 2013 at 2:33 PM, Guillermo Polito guillermopol...@gmail.com
wrote:
On Mon, Nov 25, 2013 at 5:09 PM, Stéphane Ducasse
stephane.duca...@inria.fr wrote:
From the practical point of view, it's always faster to remove.
something than to load
We have a small REPL image for Pharo 2.0
https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-2.0/job/PharoKernel2.0-OSProcess-evaluator/
It uses this code:
Hi pavel
may be I should start from your miniimage and start to making sure that the
configurations can load then in a second step
I can make sure that they can unload.
What do you think?
Stef
Hi Stef,
our starting point looks like this:
- we have a method how to produce small image without network etc.
- we are able to load network, Monticello and Gofer in it (this job is
currently broken)
- we are able to load Metacello too - this should be the basic stage for normal
users
- than
12 matches
Mail list logo