First, congratulations!
A baseline is associated with a "git version", so there is no need to
"pin the version down in a specific version" ... in a "git project" you
have the option of changing the specific version associated with a
baseline on "every commit" ....
So you would specify the BabyMock project as you would in the baseline*:
method from your ConfigurationOf and "override" the versionString in place:
spec
configuration: 'BabyMock'
with: [
spec
versionString: '1.2';
repository: 'http://smalltalkhub.com/mc/zeroflag/BabyMock/main/' ]
Note, that I'm using the more modern form of project specification....
the above is equivalent to:
spec
project: 'BabyMock'
with: [
spec
className: #'ConfigurationOfBabyMock';
versionString: '1.2';
repository ]
Dale
On 3/21/16 8:15 AM, Sean P. DeNigris wrote:
I know this is not technically a Pharo question, but I'm in China on my
honeymoon and can't access the Metacello Google group!
There was a pattern in pre-BaselineOf Metacello where one would define
dependencies loosely in the #baselineXyz:, and then pin them to a specific
version in the #versionAbc:.
For example:
baseline100: spec
...
project: 'BabyMock' with: [
spec
className: #ConfigurationOfBabyMock;
versionString: #'stable';
repository:
'http://smalltalkhub.com/mc/zeroflag/BabyMock/main/' ]
...
and then:
version10: spec
...
spec
project: 'BabyMock' with: '1.2'
...
How does one handle this sort of thing with #baseline:import:?
This is what I came up with:
version10: spec
...
baseline: 'BabyPhexample'
with: [
spec
repository:
'github://seandenigris/Baby-Phexample:INSERT-SHA-HERE/repository' ];
import: 'BabyPhexample'.
spec
project: 'BabyMock' with: '1.2'
...
But I got this error from the last line: MessageNotUnderstood: receiver of
"fetchUsing:" is nil
Thanks.
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/BaselineOf-s-and-Loose-Dependencies-tp4885749.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
