How do I create SqueakMap package for loading an MCConfiguration?

The desirable properties of a SqueakMap-based configuration are:

  - Load the application if it isn't already loaded, including any
required dependencies first, as necessary.
  - Update the package to the latest version if older version(s) are
already loaded in the image.
  - Don't lose any local changes I may have made when updating the package.
  - Load exact versions for production released versions of Squeak
  - Load the latest code for the current trunk version of Squeak

Take a look at a working example; say, the "Ma client server" package,
which meets all of the above requirements with a simple script.  It
depends on OSProcess but loads that automatically if you don't already
have it.  The "1.6" version is designated for Squeak 4.4 while "head"
version loads the currently latest code using McmUpdater, the same
process we use for trunk.

Here is some documentation:

  http://wiki.squeak.org/squeak/779
  http://wiki.squeak.org/squeak/6181
  http://wiki.squeak.org/squeak/2726

HTH

On Tue, Jan 13, 2015 at 11:08 AM, Trygve Reenskaug [hidden email] wrote:

I want to configure BabyIDE with a number of examples into a package that
interested Squeakers can install with a minimum of fuss. I chose
MonticelloConfigurations because it looked much simpler than Metacello.
Being utterly confused after reading code, the documentation I could find.
Also trying what I could guess at.

The configuration is at
    http://www.squeaksource.com/DCI/BBAllInOne-TRee.1.mcz
and at
    http://www.squeaksource.com/DCI/BBAllInOne-TRee.18.mcm

I have defined a SqueakMap package 'BabyIdeAllInOne' with 3 versions for
loading the configuration. None of them work:
I open a fresh image and use the SqueakMap Package Loader to load
BabyIdeAllInOne 1.2. I get an error
'No package release found with version TRee.1'
-----
The question appears to be:
Where did SMSqueakMap look when it didn't find a release?
I have tried these scripts (among many):
     SMSqueakMap default installPackageNamed: 'BBallInOne' version: 'TRee.1'
and
     SMSqueakMap default installPackageNamed: 'BBallInOne' version:
'TRee.18'

May be I shouldn't have used a script at all, but relied on some unknown
convention?

I'm completely lost and badly need help.
--Trygve

 Save our in-boxes! http://emailcharter.org/

1.  SqueakMap packages can be seen in the middle-left list pane of SqueakMap Package Loader. The context menu in this pane filters which packages to show. The bottom-left list pane appears to be another selection filter. I deselect all to avoid surprises.
   
2. Details about the selected package are shown in the right pane.
   
3. A selected SqueakMap package can contain releases. Available releases are listed below the package name in the  SqueakMap Package Loader.  A new release  can be created though the context menu of a selected package: "Create new Release". (There are more alternatives that I haven't investigated.)
4. Details about a selected release are shown in the right pane. One detail shown for every release is called "Download: <URL>". The URL identifies a file that specifies the installation. I have seen an .st file that will be executed as a doIt, and a .sar file that contains 3 .st files: a preamble, an installation file, and a postscript.
   
5. One command available for a selected release is "Edit release".  This opens a "fill-in-the-form" called a Release browser. Most fields are explained by hovering the mouse above the field. The exception is the bottom field; it can contain a script for the installation. I haven't found a good explanation for this script anywhere. I first thought it wasn't important because most releases shown in the package loader leave the script empty.  I now see the field as an input field. Fill it with executable Squeak code and save it. It will then be transformed into file, stored somewhere, and become retrievable through the URL in the "Download: <URL>". This scheme seems extremely powerful but only for the person who knows the various installation mechanisms.
   

• Chris pointed me to a script statement for downloading a SqueakSource package known by its URL. e.g.,
         (Installer repository: 'http://www.squeaksource.com/DCI') install: 'BBAllInOne-TRee.18' .
  this happens to be an  Monticello configuration file, BBAllInOne-TRee.18.mcm.
• Another statement I have seen is
           SMSqueakMap default installPackageNamed: '<name>' version: '<version>'
  I couldn't make it work for me, but suspect that the package shall be stored as a versioned file in SqueakMap itself.
  

On Thu, Jan 15, 2015 at 4:02 AM, Bert Freudenberg [hidden email] wrote:

On 14.01.2015, at 21:32, Chris Muller [hidden email] wrote:

Most SqueakMap packages do not have a script; they
only have a "Download URL".

They /all/ have a Download URL.  What varies is what type of file is
found at that url.  When you entered the script above and clicked
"Save" in the Release Editor browser, it saved it as a ".st" file on
the SM server, with the "Download URL" field pointing to it.
SqueakMap will still interpret .mcz, .sar, as well as .st files and
"do the right thing" for each type.

Curious, does it handle .mcm directly nowadays?

It appears not but could be done by adding new subclass of SMSimpleInstaller.