Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-26 Thread Peter Uhnák
Thank you! If the BaselineOf is independent maybe we could repurpose Versioner - because even if tags and branches are handled by git, the load order and dependencies are still required and doing that by hand is too much work. :) Also maybe the docs (which I found just now… so shame on me for not

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-26 Thread Dale Henrichs
On 2/26/15 4:41 AM, Ben Coman wrote: Just a random query (especially since I haven't played with BaselineOf and I might misunderstand something)... should #baseline: be moved out of the ConfigurationOf class so that we consistently have a BaselineOf class in both cases: git & monticello. Haha,

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-26 Thread Dale Henrichs
Martin, In my work I am moving entirely away from ConfigurationOf ... ConfigurationOf was invented because Monticello lacks the ability to reason about multi-file versions so virtually all of the meta data in a ConfigurationOf is making up for this lack. Of course, the ConfigurationOf only pa

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-26 Thread Thierry Goubier
2015-02-26 13:41 GMT+01:00 Ben Coman : > Just a random query (especially since I haven't played with BaselineOf and > I might misunderstand something)... > should #baseline: be moved out of the ConfigurationOf class so that we > consistently have a BaselineOf class in both cases: git & monticello.

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-26 Thread Ben Coman
Just a random query (especially since I haven't played with BaselineOf and I might misunderstand something)... should #baseline: be moved out of the ConfigurationOf class so that we consistently have a BaselineOf class in both cases: git & monticello. That is, the ConfigurationOfXxx.mcz package wi

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-25 Thread Martin Bähr
Excerpts from Thierry Goubier's message of 2015-02-25 15:43:39 +0100: > BaselineOf is the same as a #baseline: in a ConfigurationOf. It describes > dependencies, packages and groups for a project, without versions. On > loading, a BaselineOf will behave as a #development version in a > Configuratio

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-25 Thread Thierry Goubier
I'm sure Dale will precise this, but... BaselineOf is the same as a #baseline: in a ConfigurationOf. It describes dependencies, packages and groups for a project, without versions. On loading, a BaselineOf will behave as a #development version in a ConfigurationOf which is to load the latest versi

Re: [Pharo-users] BaselineOf vs ConfigurationOf

2015-02-25 Thread Damien Pollet
Thierry or Dale will confirm, but basically that's the gist of it. For git projects, you can specify dependencies to all things that refer to commits in git. So you can depend on a particular commit, on a tag, the tip of a branch… Therefore the release/version management part of metacello in Confi

[Pharo-users] BaselineOf vs ConfigurationOf

2015-02-25 Thread Peter Uhnák
Hi, can anybody tell me the difference between BaselineOfX and ConfigurationOfX? The only thing I've gathered is that BaselineOf is used for Git projects, while ConfigurationOf for Monticello projects; but usage-wise they seem identical. Thanks, Peter