3.3.1 for Unix
lex at cc.gatech.edu
Mon Jun 10 15:47:00 UTC 2002
David Farber <dfarber at numenor.com> wrote:
> Hmmm...and should I have expected inisqueak to transform Squeak-3.3alpha-4881.images (and .changes) into squeak.image (and .changes) when they get copied locally? Because without the transformation, I have to specify the image name when I run squeak. Just a nit.
It would be nice, for packaging Squeak/Unix, if a single VM and inisqueak
could be used with multiple images. Here's how the packaging is set up
with the Debian Squeak packages right now, for example:
VM package: holds a VM good for any image (or at least, that's the
assumption). It also includes inisqueak
inisqueak package: holds inisqueak! can work with any VM and any
sources packages: there is a sources package for SqueakV3.sources.
Theoretically there would also be SqueakV1.sources and SqueakV2.sources.
image packages: there are packages holding standard image/changes pairs
of files, including Squeak3.2gamma-4881 (or whatever the version number is).
The SF inisqueak works with any installed image. It does this by looking
in a standard location (eg /usr/share/squeak) for files named squeak.image
and squeak.changes. Typically, these are symbolic links to the real image
and changes files. This happens to mesh well with Debian, where you can
use tools to change which image and changes file the symbolic links point
Incidentally, this versioning scheme shows that you don't need
versioned subdirectories of things like /usr/lib/squeak. It's
just a small simplification, but everything helps!
More information about the Squeak-dev