----- Original Message ----- | From: "Stéphane Ducasse" <stephane.ducasse@inria.fr> | To: "Pharo Development" <Pharo-project@lists.gforge.inria.fr> | Sent: Friday, October 19, 2012 1:51:38 PM | Subject: [Pharo-project] Group metacello question | | Hi dale | | Q1: | can I have | group: 'Pharo' | | | group: 'Pharo2.0.x' | | will Pharo2.0.x only gets executed and not Pharo? when I load from | 2.0? Groups are not loaded unless you reference them in a load statement: load: #( 'Pharo2.0.x') or reference the group name in a `requires:` ... they are intended to be shortcuts or aliases for sets of packages like using the 'Tests' group for collecting all of the test packages. You _can_ use groups for naming sets of packages that refer to a platform, but the groups are _not_ automtically loaded ... | | Q2: | separated question | and how can I share spec between let say 1.4 and 2.0 | | group: 'Pharo1.4.x' | | self common: spec | the rest for 1.4 | | group: 'Pharo2.0.x | self common: spec | the rest for 2.0 | You should be using the for:do: for conditional stuff: spec for: #'pharo1.4.x' do: [ common specs for 1.4 ]. spec for: #'pharo2.0.x' do: [ common specs for 2.0 ]. If you want to know the exact platform atributes available then execute the following in an image: (ConfigurationOfYourProject) project attributes The attributes that apply: #pharo #pharo1.x, will be listed. Dale