Hi guys!

CCed the list because my answer migt be useful to someone else. I guess
nobody minds.

Ken Causey <ken at kencausey.com> wrote:
> On Thu, 2004-02-05 at 15:50, Steven Swerling wrote:
> > I think you misunderstood my question (I know how to add a new release=20
> > to a package). I was just wondering what the preferrable way is to list=20
> > it on SM2 when you have one version of the package for 3.6, and one for=20
> > 3.7 -- in separate package listings, as has been done in the past (eg.=20
> > SARInstaller for 3.2, SARInstaller for 3.4, ...), or, since it's now=20
> > possible in SM2, in a separate release within a single package.
> 
> Yes indeed I did misunderstand sorry.
> 
> I suspect you will need to talk to Goran to get the real answer.
> 
> I don't think SM2 is still very helpful for this, although just a little
> client support would make the difference.  It appears that you can mark
> each release differently in terms of what version of Squeak it supports,
> but what use of this is made if the user doesn't browse each version I'm
> not sure.
> 
> I'm CCing Goran too in the hopes that he will have a better answer.

Well, this is a good question. :) I guess the answer is "it depends".
You are right in that releases are also categorizable, so each can be
marked differently when it comes to the "Squeak version" stuff.

Sidenote: I haven't yet refined this category-stuff so that some
categories can be marked as "only for releases" and some as "only for
packages" etc.

But as of today there are a few problems using different releases for
different Squeak versions under the same package. For example, there is
no branch support yet - so if you intend to maintain these two
independently then that doesn't work.

And as you noticed - the package loader etc are also not refined for
this yet - it isn't even really refined to handle releases properly yet
(the filters mainly).

So I guess my recommendation is - if you are not going to branch, then
sure you could use a single package. And write about it in the
description so that people know about it. Otherwise I would probably go
for a separate package until we have branches added.

Any further insight into this is of course welcome. :)

> Ken

regards, Göran