Hi all!

Quoting danielv at netvision.net.il:
> Ned Konz <ned at bike-nomad.com> wrote:
[SNIP]
> > * How do I abort loading if there is a missing pre-requisite 
> > identified in the prolog, wherever it gets put?
> Right now there is no real handling of dependencies in any of the
> package tools, but this will probably change. You might want to cheat
> in the meantime, and work with a mock configuration -
> 1. Create a SqueakMap package that's an st file that itself has no
> definitions, but only a script loading a list of applications in order
> (loading only what's missing). This is your configuration package.
> 2. Create you other SM cards for the packages that include the code.
> Note in their description that they have prerequisites, and should be
> loaded through the configuration package.
> 3. In SqueakMap, you put packages in version categories (Squeak3.2) to
> indicate compatibility. Put only give only the configuration package in
> such a category, and people using the miniloader will by default see
> only it.
> 
> Extending a snippet Goran sent a short while ago, this is a sketch for
> your configuration .st package
> 
> sm _ SMSqueakMap default loadUpdates.
> {'ConnectorFixes'. 'ConnectorsModel'. 'ConnectorsMorphs'.
> 'ConnectorsIntegration'} do: [:packageName |
>  (SMInstaller forPackage: (sm cardWithNameBeginning: packageName) 
> 			directory: FileDirectory default) install 

Yes, this "trick" should work. Has anybody tried it? And... should we use it? ;-)

Either we say that, yeah, go ahead and write "meta packages" in .st format like
the above. That would make it possible to do many, many fun things...

Or we try to be a bit declarative instead and add dependencies to SM. And
versions of packages. And conflict resolution... :-)

Of course, until we do that we can always use the "meta package" trick.

What do you think?

regards, Göran

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