Anybody want to help us Guides fix a process bug? (was: Re: [
Fwd: Package Loader version filtering ...
rwithers at quallaby.com
Wed Feb 12 22:13:01 UTC 2003
> -----Original Message-----
> From: Daniel Vainsencher [mailto:danielv at netvision.net.il]
> Not sure I understand what you mean. Note that SM uses
> categories right,
> and SM loader simply checks whether the current squeak version matches
> one of those categories for each package.
The SM issue that occurred when the image version changed, for both 3.2->3.4
and for 3.4->3.5, was that the SM cards for the now previous image version,
would not show up when using a new image version + SM. Many of the solutions
are sounding quite complicated, and maybe they need to be when discussing
dependencies of modules. However when talking about base squeak versions,
all cards should show up if they have been registered for any previous
version of base squeak.
For example, I look at Connectors and SM has required that categories be
installed for #('Squeak3.2.1' 'Squeak3.4' 'Squeak3.5'), so that it works on
all of those systems. My proposal is that you just need to enter
'Squeak3.2.1' and any later base image versions will be able to see and load
that SM entry, without the package maintainer having to add yet another
category, for each new image release. This is especially true as the image
starts to get re-ginsued. A more rigorous dependency mechanism could be
used to check and auto-load auxiliary packages at specific version levels of
support. This version info should be put in the dependency mechanism, but
not in the card-catalog system.
my 0.02 centimes
More information about the Squeak-dev