Quoting David Faught <dave_faught at yahoo.com>:
> My specific question is this: when a new version of something on
> SqueakMap is developed, should a new package be registered, or should
> the existing package be editted to reflect the new version?

The existing package registration should be edited and the "version" field
should be changed and also the download url. Unless you have a download url
which doesn't change.

> If the latter is true, then this says that older versions of packages
> just go away.  It seems to me that older versions are sometimes very
> usefull.  Anyway ...

Exactly. This is a known "simplification" in the 1.0x versions of SqueakMap. I
am working on 1.1 which has support for "package releases" so it will remember
the older versions. This is essential to handle dependencies etc.

SM1.1 will probably not be released until after christmas. The most important
change is the addition of "package releases" but it includes a lot of other new
good stuff we need, like for example links between packages and a new kind of
"registration" called a "resource".

> My more general question is this: there are some simple directions for
> SqueakMap users; are there some directions somewhere for SqueakMap
> package developers?

Well, actually - today I wrote a bit in the FAQ on the Squeak Swiki.
Should of course write down more. Or someone else could help me! :-)

regards, Göran

Göran Hultgren, goran.hultgren at bluefish.se
GSM: +46 70 3933950, http://www.bluefish.se
\"Department of Redundancy department.\" -- ThinkGeek