There are a number of changes that take effect with the 1.0-beta.8 release (part of the reason that the release has taken so long):
- Use Metacello for package management.
- Use Gofer for manipulating mcz files.
- Use Gofer Project Loader for managing Metacello configurations.
- Use glassdb wiki for web-based GLASS documentation.
- Use glassdb issue tracker for GLASS bug reports.
- Use Help System for image-based documentation, especially useful for installing GCI library files and defining GemTools Sessions.
- Use GemTools for updating the GemTools client code and updating the fundamental GLASS packages.
- Use Gofer Project Loader to upgrade the optional projects (which includes Seaside28, Seaside30 and SOAP)…Yes Seaside and SOAP are no longer included in the default configuration.
There are outstanding tasks that need to be completed before the entire 1.0-beta.8 release process is complete and you should keep an eye on the 1.0-beta.8 Release tasks for monitoring progress towards completion. Here is a list of the major milestones that are pending:
- GemTools 1.0-beta.6 one-click release.
- GemStone/S 2.4.x download with 1.0-beta.8 installed.
- New GLASS Appliance based upon GemStone/S 2.4.x and 1.0-beta.8.
- 1.0-beta.8 bootstrap release.
- Seaside 3.0 and GLASS documentation.
With all of that said, 1.0-beta.8 is ready to be used:
- Upgrade path for nearly all previous GLASS versions, including the problematic Pier upgrade issue.
- The GemTools documentation in Terse Guide to the (new) GLASS Tools has been transfered (and updated) to the glassdb wiki see the GemTools Launcher Guide page.
- Detailed upgrade instructions have been created on the glassdb wiki see the Getting started with GLASS page.
So have at it and let me know if you have problems.
1.0-beta.8 Upgrade Instructions
If you have an existing instance of GLASS including:
- a GLASS installation with version GLASS.230-dkh.231 or earlier
- a GLASS Appliance 1.0beta11 (GLASS.230-dkh.164)
- a native install of GemStone/S 64 2.3.1
- a native install of GemStone/S 64 2.4.x (contact me for download instructions)
Upgrade your installation by following these steps:
- Create a GemTools client image (Steps 3 through 8 on the Getting started with GLASS page) based upon Pharo or Squeak
- Make a backup of your starting extent (Step 9 on the Getting started with GLASS page)
- Update GLASS to 1.0-beta.8 (Steps 10 and 11 on the Getting started with GLASS page)
If you have upgraded from a version earlier than 1.0-beta.0, then you are done! The upgrade for optional projects was performed as part of the GLASS update.
If you are upgrading from 1.0-beta.0 or later, then you are not quite done with the upgrade process.
Upgrade Optional Projects for 1.0-beta.0 and later
The 1.0-beta.8 GLASS configuration no longer manages all of the GLASS projects directly. Only a handful of fundamental GLASS projects are being managed. To finish the upgrade process you will need to individually upgrade the optional projects like Seaside28, Seaside30 or SOAP.
For post 1.0-beta.0 upgrades, you should pick and choose from the projects and load only those projects that you are using or want in your repository.
Any one of the above configurations can be loaded on top of GLASS 1.0-beta.8.
Using Gofer one can load the latest version of Magritte using the following expressions:
Gofer new gemsource: 'MetacelloRepository'; package: 'ConfigurationOfMagritte'; load. (Smalltalk at:#ConfigurationOfMagritte) project latestVersion load.
Even though Gofer drastically reduces the complexity of the load expressions involving Monticello, there is still room for improvement when loading configurations and that’s where Gofer Project Loader comes into play.
Gofer project load: 'Magritte'.
With Gofer Project Loader you can specify a default repository (for GLASS: http://seaside.gemstone.com/ss/MetacelloRepository). Gofer Project Loader is also aware of the ‘ConfigurationOf’ convention, so it isn’t necessary to type the leading ‘ConfigurationOf’.
The Gofer Project Loader expression:
Gofer project load: 'Magritte' version: '184.108.40.206'.
loads version ‘220.127.116.11’ from ConfigurationOfMagritte and:
Gofer project load: 'Magritte' version: '18.104.22.168' group: 'Magritte-Seaside'.
loads the ‘Magritte-Seaside’ package (along with the dependent packages of ‘Magritte-Seaside’) from version ‘22.214.171.124’ of ConfigurationOfMagritte.
The following Gofer expression is useful if you would like to just load the ConfigurationOfMagritte without loading the Magritte project itself:
Gofer new gemsource: 'MetacelloRepository'; package: 'ConfigurationOfMagritte'; load.
It should be obvious by now that it will be worthwhile spending some time learning about Metacello (take the Metacello Tutorial), Gofer and Gofer Project Loader. I think you will find Metacello it very useful to build a Metacello configuration to manage the packages in your own project.