Peter wrote: >It all looks a maze of >new terminology to me - I don't understand the difference between Monticello >and Metacello, for instance.
Both are part of configuration management. Historically, Monticello came first. It supports distributed version control of a single package. Package is a problematic concept in Pharo (and Squeak), as multiple class categories belong to one package. Class category and package are often used as if they are the same. The Magritte-Model package contains all categories starting with 'Magritte-Model', a.o. Magritte-Model-Core. Monticello has support for required packages, but this is better expressed in Metacello. Metacello solves the problem of dealing with multiple platforms, dependencies of packages and different status. Better and longer explanations can be found in the Deep into Pharo book http://www.deepintopharo.com >I am sure to an expert your explanation of how >to check the correct version of Magritte3 is quite straightforward, but I >would never have found my way to that conclusion myself. Yes, that takes time and experience. A smalltalk system is large and finding your way around is not simple. I hope explaining how I find out helps. >As I pointed out to >Esteban, I used the configuration browser on 5 May to get the stable version >of Magritte3. If that was already out of date, I am pretty well lost. There was no test for this, so the build was green :( >Still, I am making progress with my original aim of learning about Magritte, >and there are many helpful people on this group, so you can just regard this >as me blowing off steam after things had not gone completely easily. Good. Just continue telling us where we need to improve. Stephan
