[ANN] SM2 pre-alpha

goran.krampe at bluefish.se goran.krampe at bluefish.se
Wed Oct 15 09:40:00 UTC 2003


Hi all!

First of all, Daniel has done a good job here. I want you people to:

1. Use this as ... well, as a kind of preview. The base code used in
this client has evolved further since Daniel did this - so don't expect
it to be the same when SM2 goes live "for real".

2. Be gentle. The idea Daniel has used - to simply analyze the log of
SM1 - to generate releases etc is of course a bit of a "hack". But it
works! And he did in very short time, so "there may be tigers here".

3. I have fixed a couple of problems (Daniel's procedure forgets all
installed packages) and also fixed some bugs. I am sending these changes
to Daniel so there will probably be a new release today.

4. This code is also missing some of the fixes I did in 1.09 which I
will fold in later.

So... again - this is preview/play-with stuff. Sure, you can report bugs
- but don't expect us to necessarily fix them because we are busy
getting the "real stuff" working too. :-)

Daniel Vainsencher <danielv at netvision.net.il> wrote:
[SNIP]
> The whole story - 
> Goran and I have agreed to create an SM2 client that works with the old
> SM1 servers as a stepping stone to SM2. This provides us with package
> releases, which means that if you have this client installed, you can
> install old releases of any package (*). This also lets you execute
> loadscripts that specify the version of the package wanted, like this - 
> (SMSqueakMap default installerForPackage: ((SMSqueakMap default
> packageWithName: 'BFAV ') releaseWithVersionString: '1.26')) install

One thing we don't get with this hack is UUIDs for the releases. When
the server arrives we will have that and the above will be able to be
written like:

SMSqueakMap default installPackageReleaseWithId:
'b942bb71-eb21-4b48-b2b8-6ede7755513e'

(faked UUID)

> The idea behind this release is to provide releases early, so that we
> can eliminate spurious package forks and start experimenting with the
> better packaging practices this makes practical (versioned loadscripts).

This is btw what SM refers to as "static loadscripts". See category:

http://map1.squeakfoundation.org/sm/category/b942bb71-eb23-4b48-b2b8-6ed
e2455513e

The idea is that the load script, since it is referring to specific
releases (and thus can't change), produces the same result (if applied
to the same image) now and in the future.

regards, Göran



More information about the Squeak-dev mailing list