Re: [Pharo-users] Iceberg + BaselinOf + Metacello - how to manage interdependencies ?

Nobody knows ? I probably do/ask something wrong… My impression is that it is very difficult for a newcomer to get into Iceberg/Github (I tried to avoid GIT as much as possible and I understand why now ^_^)… but still it’s a great tool. Just not that easy to "master" (there are several possibilities, orders for code loading). Please tell me if there is something wrong in what I try to do. Cheers, Cédrick

I’m trying to declare a BaselinOf to load lots of Packages. My aim is to have a kind of distribution (so students don’t have to load packages). I’m new to Iceberg + BaselinOf + Metacello. I target only P7.

Let's say I want to load Teapot and NeoJSON (development version). Teapot depends on NeoJSON (#stable).

So, whatever the order of declaration in the BaselineOfMyProject, I’d like not to have the following conflict:

<unknown.png>

So is it possible to tell to load :

- Teapot , then NeoJSON (updating to NeoJSON the dependancies of Teapot) - NeoJSON (#latest) then Teapot (ignoring the NeoJSON stable of Teapot baseline).

I know I risk breaking Teapot (but I don’t care :), I want latest NeoJSON.

So is it possible to define such constraints ?

I’m aware of that way of loading from Metacello :

Metacello new baseline: 'NeoCSV'; repository: 'gitlocal://../../iceberg/svenvc/NeoCSV <gitlocal://../iceberg/svenvc/NeoCSV>' ; onConflict: [ :err | err useIncoming ]; onUpgrade: [ :err | err useIncoming ]; load Still, not sure, of the meaning of #useIncoming (#allow #disallow). 1) Does one mean keep/load the latest ? 2) is it possible to launch such Metacello installation from Iceberg ? <PastedGraphic-2.png>

TIA,

Cédrick