Hi Uko, If I understand your need correctly, I would say yes : you can add a spec repository: anUrl inside the version and this should override the repository inside the baseline method. If you're ready to try some of the new stuff pushed in Metacello by Dale, I would suggest that you create a BaselineOfYourProject inside your branch and write a configuration which refer to the baseline; there, just changing the url to point to your branch would make it work. inside the version method, for example: (gitfiletree url) spec blessing: #development; author: 'ThierryGoubier'; baseline: 'AltBrowser' with: [ spec repository: 'gitfiletree:// github.com/ThierryGoubier/AltBrowser.git?branch=pharo4.0' ]; import: 'AltBrowser' (It's also quite convenient to be able to work with metacello scripts which are as short as loading the configuration in the first place: Metacello new baseline: 'AltBrowser'; repository: 'gitfiletree://github.com/ThierryGoubier/AltBrowser:pharo4.0 '; load And you can then customize your dependencies per branches, by modifying the BaselineOf in each. Thierry 2015-02-01 16:21 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
Hi,
I'm using git for versioning, and usually I just work with master branch. Now I have created another branch, can I create at least temporal symbolic version that will work on a current baseline, but will use different "repository" and so other branch? Or is there another good way to handle branches?
Uko