John Pierce <john.raymond.pierce at gmail.com> wrote:
> > I haven't had time to look at this but if it uses SM the way it ought to
> > - then SM uses the client cache so if the releases are there then it
> > will not need a connection.
> 
> I use the following code to install each SM package:
> 
>   SMSqueakMap default installPackageNamed: packageName autoVersion: version

Looks fine. :)

> I also preceed the installation of all the SM packages with a call to:
> 
>   SMSqueakMap default loadFull.

Yeah, or loadUpdates (which currently always does a full). This makes
sure that the local map is up to date.

> So if that is the "correct" way to engaging SM then I guess I am covered.
> 
> > Further - this mechanism for SM can be integrated into SM if you want
> > to. We can take a look at it as soon as I get my dependency stuff
> > properly running.
> 
> That is a nice idea.  I think the only goofy thing you'd have to
> consider is that conceptually I think it is just as important to
> provide a way to install MCZ packages as seemlessly as SM packages.  I
> cover both cases with the same simplistic interface.  I am not sure
> you'd want to incorporate that aspect into SM.

We can take a look at it later on. SM already has some MC integration so
some more may be just fine. :)

regards, Göran