Not really, this isn't the same situation as the Connectors/SAR one,
because the base installer is SM itself. The script can just say
"SqueakMap: load SARInstaller and then load my package using it". No
need to find the stream, because the load script can be external to the
package.

This is a benefit of holding dependencies externally to the packages -
it's should be easy to simply compose packaging work.

Daniel

Ned Konz <ned at bike-nomad.com> wrote:
> On Saturday 30 November 2002 09:26 am, Doug Way wrote:
> > I think that would be simpler than requiring all package owners who
> > use the SAR format to have a special load script to install
> > SARInstaller
> 
> The problem with this is back to the "self-installing archive" 
> problem: we'd then need to put that script in the front of the SAR, 
> and it would have to crawl up the stack contexts to find the stream, 
> etc.
> 
> I think a better strategy would be just to notify the user when no 
> installer is available. Which would go along with the "better error 
> reporting" that we want for SM loading in general.
> 
> -- 
> Ned Konz
> http://bike-nomad.com
> GPG key ID: BEEA7EFE