19 May
2009
19 May
'09
1:54 p.m.
On 19 mai 09, at 12:05, Alexandre Bergel wrote:
Importer will not complain, but all classes will appear in
'Unpackaged' packages, and it takes more time because my code is buggy
in this area
With the
latest Moose update, it is now possible to load Pharo into
Moose in less than a minute.
However, after loading Moose, you need to run PackageOrganizerCache
buildSystemCache (it takes less than 2 minutes to run).
Not sure if I really want to store this cache in MC for the moment
What happens if one forget to do so? Why the cache is not build on demand?
Because this is a workaround and I didnt want to think too much about
it. This is more of a Pharo issue with the lack of first-class packages.
We should talk about this.
--
Simon