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?

tim
--
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Strange OpCodes: COMB: Straighten Wires