Hi Hannes, I had to do a lot of research to answer your question.

That's certainly valid use-case for simple packages, and the flexible
Category model of SqueakMap's domain model supports it now.  Its also
easy enough to update the UI to support it too (see my Inbox
submission).

Unfortunately, its the SMServer which currently, for some strange
reason, wants to have a single Squeak version associated with a
Release.  Note the web site presents it as a drop-down as well, so it
seems intentionally limited to one primary version, but I'm not sure
why.  I imagine when someone re-writes the SMServer that will be
fixed.

For 5.1, it appears we still have to go through the process for each
package if we wish for them to appear in the 5.1 list.

 - Chris

On Mon, Aug 15, 2016 at 10:51 PM, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> The instructions seem to cover the case where an updated version of
> the package is necessary.
>
>
> What is missing is the answer to the following questions:
>
> What are the instructions if when the current package runs fine in 5.1
> and thus no new release of the package is necessary?
>
> Is it still necessary to copy the load script or can the Squeak5.1
> category be added to the existing entry?
>
> On 8/16/16, Chris Muller <ma.chris.m at gmail.com> wrote:
>> Its a pain, but it only takes a few minutes, so I documented the
>> current state of my main projects on SqueakMap.
>>
>> This also means they show up in the catalog list for 5.1, of course.
>> The longer the list, the better it looks (at ESUG, etc.).
>>
>> I freshened the instructions here:
>>
>>    http://wiki.squeak.org/squeak/6180
>>
>>
>