Hi all!

Quoting danielv at netvision.net.il:
> You're right - SqueakMap is a catalog. It's purpose is to make package
> visible and easily installable. It doesn't explicitly manage conflicts
> or dependencies.

True. And since the new Modules system has that stuff "built in" it felt stupid
to reinvent the wheel (even though it could be useful for "old" packages).

Anyway, SqueakMap is intended to be quite "simple" but effective. I don't want
it to become too complicated - and dependency management is one of those areas
that quickly gets really tricky...

> There is a nice trick we could use to help with dependencies: upload a
> package that loads other packages, like this -
> 
> packages _ {'Refactoring Browser'. 'SM Package Loader'} collect:
> [:packageName | 
> SMSqueakMap default cardWithName: packageName].
> packages do: [:package | (SMInstaller forPackage: package directory:
> package downloadUrl) install]
> 
> Just put something like this in an .st.gz file somewhere on the web,
> register your package using the web form at
> http://marvin.bluefish.se:8000/sm/regpackage, including the download
> url, and that's it, anyone can now load all required components in
> proper order.

Yes, I have also been thinking of making "meta packages" like this. Great to see
that Daniel is already way ahead of me. :-)

Since a package can be just a .st or .cs file packages such as the above is
quite feasible and could also be a way of expressing not only dependencies but
also "configurations" that Daniel has been talking about.

regards, Göran

PS. Daniel, I have read everything you have written, will get back to you later
today - gotta meet a client etc first. :-) And thanks for writing that summary. DS

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