I added: \subsection{How to Deal with Package Structure Changes?} Imagine that you want to develop an application on both Pharo13 and Pharo14, and that your application has only a package for one version: either because you changed your application or because the package was integrated into the base system. The solution is to define the dependencies and use the symbolic tag as a marker, as follows: \begin{code}{} spec for: #'pharo' do: [ spec package: 'that depends upon zinc' with: [ "the common required packages for your package" ]. spec for: #'pharo1.3.x' do: [ spec project: 'Zinc' with: [ spec className: 'ConfigurationOfZinc'; versionString: #'stable'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]. spec package: 'that depends upon zinc' with: [ spec requires: #('Zinc') ]. ]. \end{code} If you use the \ct{stable} version in your baseline there is no need to anything special in your version specification. stef
Stef
Haha, no problem at all ... glad to help:)
Dale
----- Original Message ----- | From: "Francois Stephany" <tulipe.moutarde@gmail.com> | To: pharo-project@lists.gforge.inria.fr | Sent: Tuesday, April 24, 2012 4:53:21 PM | Subject: Re: [Pharo-project] How to declare Zinc/FS dependency in Metacello Configuration for 1.4 | | Haha you made my day Dale! | I didn't know that you coul specify #'pharo1.3.x' in the baseline. | That's exactly what I was looking for. | | Sorry for the noise! | | On 24/04/12 16:49, Dale Henrichs wrote: | > spec for: #'pharo1.3.x' do: [ | > spec project: 'Zinc' with: [ | > spec | > className: 'ConfigurationOfZinc'; | > versionString: #'stable'; | > repository: 'http://www.squeaksource.com/Metacel | |