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 the past
with mcz repos, one could refer to a specific version of each package, but
now you would only be able to specify a version for the whole git repo.

I was about to ask that after reading through Metacello docs �� While I find usefull to define groups and dependencies at package level (I need only package A from ThatProject on version 2.6, cool!), I didn't understand why define version at package level.... If many dependencies exists to different versions of different packages belonged to the same project, doesn't that means (or is an indicative) that those packages should be separeted in different projects? I don't think this constraint will be a problem.

On Thu, Dec 21, 2017 at 12:37 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:

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

CyrilFerlicot wrote
> So, you just need Metacello to manage the dependencies... This is what
> BaselineOf do. You just manage the dependencies part and
> not the versionning part that is already managed by git.

A BaselineOfXyz is very similar to what configurations did for #1, with a
few simplifications (e.g. you don't need to declare the method a "baseline"
or specify a repo because you obviously already know the repo because that's
where you just got the baseline itself)

CyrilFerlicot wrote
> The equivalent of a ConfigurationOf version in now the SHA of a commit or
> a tag/release
> of git).

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 the past
with mcz repos, one could refer to a specific version of each package, but
now you would only be able to specify a version for the whole git repo.

HTH

-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html