Dimitris, This is your baseline method and I'm not sure what you consider "an ugly hack": baseline: spec <baseline> spec for: #'pharo' do: [ spec package: 'Octopus' with: [ spec requires: #('Pillar') ]; configuration: 'Pillar' with: [ spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main'; version: #'development' ] ] Is it the fact that you have to include #development instead of #stable in your baseline? If so , you can make a pre-load decision to use the development version of Pillar by using a Metacello lock: Metacello new configuration: 'Pillar' version: #development; repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main'; lock. Then you can change your baseline back to using #stable or whatever and when you load the Octopus project, using 'Metacello new', the #development version should be used ... Or is there something else that you consider "an ugly hack"? Dale On 10/23/16 6:46 AM, Dimitris Chloupis wrote:
I have a baseline in my github repo for a tool I am making and I have included the pillar development dependency via an ugly hack , whats it the proper way of doing this ?
https://github.com/kilon/Octopus/blob/master/BaselineOfOctopus.package/Basel...