|
Le 25/05/2015 01:13, Yuriy Tymchuk a écrit :
> Hi,
>
> for some time now I was using baseline in my projects for basing
> dependency support and git tags for versioning the releases. Then
> I’ve just pointed to the releases from a configuration to be able to
> put my project in the conf. browser.
The way to go, in my opinion :) So much simpler.
> Now when I what to depend on a project which has a baseline, can I
> depend directly, or should I make a configuration. In my opinion the
> latter one is a pain, as essentially I just putt a version methods
> and then provide there urls with same name git tags.
You can have a baseline which depends on another baseline, with the
following in your baseline:
spec
for: #common
do: [
spec baseline: 'AltBrowser' with: [ spec repository:
'github://ThierryGoubier/AltBrowser:pharo4.0' ].
...
It's a bit harder if you only want to load a package or a group inside
that baseline. You can import the baseline, and then all names defined
by that baseline will be available as dependencies.
Regards,
Thierry
>
> Cheers! Uko
>
|