Re: [Pharo-users] Iceberg, Git and Package version

Hi Stef For example, my project can depend on Iceberg using the following definition: spec baseline: 'Iceberg' with: [ spec repository: > 'github://pharo-vcs/iceberg/:' ]; But now suppose my project have one package that depends on Iceberg "minimal" and other that depends on the "default" group

Re: [Pharo-users] Iceberg, Git and Package version

Hi vitor I'm sorry but I do not understand your question? can you rephrase it and give an example? Stef On Sat, Dec 30, 2017 at 10:03 PM, Vitor Medina Cruz wrote: > Hello Stephane > > What if I want to define two projects for the same baseline: both pointing > to different groups? > > >

Re: [Pharo-users] Iceberg, Git and Package version

Hello Stephane What if I want to define two projects for the same baseline: both pointing to different groups? Livre de vírus. www.avg.com

Re: [Pharo-users] Iceberg, Git and Package version

>From a baseline you can refer to a none github configuration here is an example from the pillar newpipeline dev branch it shows you both: dependencies on github projects and smalltalkhub baseline: spec spec for: #common do: [ spec blessing: #baseline. spec repository: 'http://smalltalkhub.com/

Re: [Pharo-users] Iceberg, Git and Package version

> > This is mostly true, but ATM you may want to wrap your BaselineOf in a > ConfigurationOf (i.e. refer to A with a SHA from B) for tool integration > e.g. only Configs show up in the catalog. IIUC, one additional constraint > to > be aware of (not sure how important it is in practice) is that in

Re: [Pharo-users] Iceberg, Git and Package version

But what about versioning of my external dependencies (such as other projects)? I do that on the baseline too? The idea in the future is to abstract versioning away from git into Iceberg? On Thu, Dec 21, 2017 at 11:49 AM, Cyril Ferlicot D. < cyril.ferli...@gmail.com> wrote: > On 21/12/2017 14:43

Re: [Pharo-users] Iceberg, Git and Package version

CyrilFerlicot wrote >> Now I got lost A ConfigurationOfXyz was doing two things: 1) Declaring the project structure of packages and their dependencies in a #baselineXyz: method 2) Tagging specific sets of package versions with meaning symbolic to the project e.g. 1.2 or stable or whatever CyrilF

Re: [Pharo-users] Iceberg, Git and Package version

On 21/12/2017 14:43, Vitor Medina Cruz wrote: > Now I got lost, I had understand that a ConfigurationOfXXX is my project > definition and that Iceberg is just the Pharo VCS (in substitution of > monticello). Iceberg is now my project? How do I configure my > dependencies, groups and versions? The

Re: [Pharo-users] Iceberg, Git and Package version

> > Package versions do not have any sense on iceberg, where what has sense is > the “project” version. All packages point to a commit in repo. > Oh, I suspected that, but was unsure :) the thing is: you don’t use configurations with iceberg projects, you use > baselines. > Now I got lost, I had

Re: [Pharo-users] Iceberg, Git and Package version

> On 21 Dec 2017, at 11:03, Vitor Medina Cruz wrote: > > 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 > > spec for: #common do: [ > spec ble

Re: [Pharo-users] Iceberg, Git and Package version

> On 20 Dec 2017, at 19:51, Vitor Medina Cruz 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 version

Re: [Pharo-users] Iceberg, Git and Package version

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 > > spec for: #common do: [ > spec blessing: #beta. > spec > package: 'CoolToolSet-Core' with: 'CoolToolSe

Re: [Pharo-users] Iceberg, Git and Package version

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

[Pharo-users] Iceberg, Git and Package version

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: ; which I think is a pattern used by Monticello, right? However, I can't