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 versions of the packages listed (and whatever dependencies listed).
BaselineOf becomes very convenient when you combine that with a repository which understand branches, such as git. Then, you say which branch or release tag you want through the repository url, say it's a baseline, and, et voilà, you have it (it loads the latest version on that branch or tag). Repositories urls which support branches and tags are github:// and bitbucket:// urls; which support branches (and not tags) are gitfiletree:// urls. Really, really makes things a lot easier than configurations. Took me a while to start using it, now, can't do without. These days, I'm just using Metacello scripts to load stuff out of baselines instead of configurations for allmost all my stuff. Thierry 2015-02-25 15:25 GMT+01:00 Damien Pollet <damien.pollet+ph...@gmail.com>: > 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 > ConfigurationOf... becomes mostly irrelevant, since you can encode it in how > you organize and use your git repo. > > On 25 February 2015 at 13:47, Peter Uhnák <i.uh...@gmail.com> wrote: > >> 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 >> > >
