Hi Tim!

Trying to throw in some answers before getting back to building my
veranda...

Tim Rowledge <tim at sumeru.stanford.edu> wrote:
> Can anyone explain to me the relationship between SM loading a package,
> DVS thinking it has a package, the changeset name resulting from filing
> in a package and the price of fish?

:-)

> I just loaded the Balloon3D package via SM and got 8 DVS packages and 8
> changesets with the same names - but the files in the Balloon3D.sar all
> explcitly register the DVS packages.
> I also loaded the VMMaker package and got a DVS package called VMMaker
> (no explicit register in the filein) and changeset named VMCodePackage
> (after the file name).
> 
> What's happening here?

Which packages DVS knows about has nothing to do with SM.

Sidenote: Which packages SM thinks are installed is kept in a Dictionary
in instvar installedPackages in the SMSqueakMap instance. You can easily
modify it if needed.

Perhaps if you have subclassed PackageInfo there will not be an explict
register-statement in the fileout? Just a guess. My HttpView package has
no such subclass of PackageInfo and it does contain a register-statement
at the end.

Then, regarding names of changesets I guess it has to do with how the
DVS files got filed in. Eh, wait a minute... VMMaker is published as a
changeset - not a DVS filein!

So it will be installed using code in SM (SMDefaultInstaller>>fileIn) -
which derives the changeset name from the filename of the changeset.

How Balloon3D (using DVS and SAR) picks the changeset names I don't
know.

Regarding price of fish I am not sure. :-)

regards, Göran