Keith Hodges wrote:
Chris Muller wrote:
Hi Igor, I think you may be right. But can you elaborate a little?
Over the last week or so, I developed a "SarBuilder2" which does all the hard work of making the complex object that is a SAR. It calculates prereqs and determines the correct load order, and creates the load script and writes out the ZipArchive to a .sar file of your choosing. Absolutely wonderful.
One reason I like using "SAR" as my "Installer" because I sometimes need *objects*, not just code, to be brought into the object system.
Still, I have had some positive exposure to "Installer" which, unfortunately, is not included with 3.9 :(. I see it can load Monticellos, change-sets, SqueakMap packages, etc. That's all great, but I guess SARInstaller can do that too, and its included with 3.9.
Regards, Chris
Chris, why dont you use LPF, magma was one of the reasons that I implemented it. Magma users use a variety of images and Magma needs you to have MCConfigurations working. Thats what LevelPlayingField in LPF gives you.
http://installer.pbwiki.com/LevelPlayingField
Also the issue of extensions to classes that don't exist in older images is solved via the orphanage. MC1.5 doesnt complain like MC1 does.
Further there is a place for publishing simple Installer based load scripts that may differ slightly between images in squeaksource/Installer/Installer-Scripts.
Matthew Fulmer and I want to be able to generate SAR's from Installer scripts. Your SARBuilder looks like it would be a cool to have it generate from Sake/Packages definitions, once you have Sake/Packages loaded with the dependencies. Why not try using a Sake/Packages micro universe as I described in a recent email to squeak-dev an example is available in squeaksource/Jetsam Client-Packages.
We have lots of ways of doing stuff now.
Keith
magma@lists.squeakfoundation.org