Then in a Metacello configuration should I reference the hash git commit or
a tag in a version method? For example, an extract from Deep in Pharo:
ConfigurationOfCoolToolSet>>version02: spec
> <version: '0.2' imports: #('0.2-baseline' )>
> spec for: #common do: [
> spec blessing: #beta.
> spec
> package: 'CoolToolSet-Core' with: 'CoolToolSet-Core-AlanJay.1';
> package: 'CoolToolSet-Tests' with: 'CoolToolSet-Tests-AlanJay.1';
> project: 'CoolBrowser default' with: '1.3';
> project: 'CoolBrowser Tests' with: '1.3'].
>
In this case 'CoolToolSet-Core-AlanJay.1' would be changed by
'CoolToolSet-Core-<git_hash>'?
On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse <stepharo.s...@gmail.com>
wrote:
> In iceberg you can specify
> - latest version when you do not specify anything
> - a version (but it should be a git tag so you should save you code
> with a tag - iceberg does not support it right now but you can do it
> with git)
> - the hash of your git commit.
>
> Does it answer your question?
> Stef
>
>
> On Wed, Dec 20, 2017 at 7:51 PM, Vitor Medina Cruz <vitormc...@gmail.com>
> wrote:
> > Hello,
> >
> > How are packages versions computed in Iceberg?
> >
> > I am looking at the Metacello documentation at 'Deep in Pharo', it says I
> > can define dependencies at package level and it uses the following
> format to
> > identify versions: <dev_name.versionNumber>; which I think is a pattern
> used
> > by Monticello, right? However, I can't figure what is the equivalent (if
> > any) in Iceberg.
> >
> > Thanks in Advance,
> > Vitor
>
>
