Lukas Renggli wrote:
>> It would be far more useful to have Sake/Packages definitions from the
>> outset. Why not have a new class PackagesSeaside, or even just Seaside.
>> Why not do it the other way around, define the dependencies in
>> Sake/Packages and build the builder on top of that. It will even sort
>> the load order for you.
>>>> I've added an experimental export option for Sake/Packages. I tried to
> add as much meta-data as possible and it seems to work.
>>cool, very insteresting.
> I don't know how useful this is though.
The sake packages version can simply have all of the definitions, it
shouldn't need the seaside interface.
> Seems to be less intuitive
> than the other two options and is takes a very long time to load even
> a small code base.
You are loading Installer and all of the package definitions for every
package supported by squeak. If someone is building an image using
Sake/Packages they will have all that loaded already in the base image
from which they are starting.
Also MC1.6 (with SystemEditor enabled) is 3 times faster than MC1.
> Maybe there is something wrong with the
> Sake/Packages definition?
>>perhaps, it looks ok though.
> Cheers,
> Lukas
>Keith