as far as I understand it, you have this:
Calypso v1
- Commander v1
- ClassAnnotations v1
You are working on and you fix a version in ClassAnnotations
Calypso v1
- Commander v1
- ClassAnnotations v2
but you still do not want to make it as a release. When rebuilding your
image, you want to be able to load all three packages in the latest state.
Then you make a new change in Calypso
Calypso v2
- Commander v1
- ClassAnnotations v2
and you want to mark this dependency tree as a new release version
-- Pavel
2018-03-05 16:57 GMT+01:00 Guillermo Polito <guillermopol...@gmail.com>:
> But can you explain me the scenario? I still don't understand it :(
>
> On Mon, Mar 5, 2018 at 4:51 PM, Denis Kudriashov <dionisi...@gmail.com>
> wrote:
>
>> Maybe we should just load Calypso dependencies explicitly.
>> In any case they will be used by other projects. Like new Iceberg will
>> use Commander. And ClassAnnotation will be in Kernel.
>> So we will need to load them in another time than Calypso.
>>
>> Now we can just put them directly into #loadCalypso method. (there are
>> three dependencies)
>> It will fix my problem and make Pharo build reproducible.
>>
>> 2018-03-05 16:38 GMT+01:00 Guillermo Polito <guillermopol...@gmail.com>:
>>
>>> But, "one single class" does not mean anything. Because it depends from
>>> which branch/commitish you are loading it from...
>>>
>>> Can you explain better what is the problem because I am not getting it...
>>>
>>> In any case, independently of where is the burden, I want to veto any
>>> new integration that may make future builds non-reproducible. Otherwise
>>> this is a source of chaos and dead kittens.
>>>
>>> On Mon, Mar 5, 2018 at 4:17 PM, Denis Kudriashov <dionisi...@gmail.com>
>>> wrote:
>>>
>>>> 2018-03-05 16:13 GMT+01:00 Cyril Ferlicot <cyril.ferli...@gmail.com>:
>>>>
>>>>> On Mon, Mar 5, 2018 at 4:10 PM, Denis Kudriashov <dionisi...@gmail.com>
>>>>> wrote:
>>>>> > Hi Pablo.
>>>>> >
>>>>> > Dev branch approach not really works. Because any merge into master
>>>>> will
>>>>> > break master baseline. (notice that baseline is in same repo).
>>>>> > And managing merges by hand all the time is not a solution.
>>>>> >
>>>>> >
>>>>> Hi!
>>>>> If you don't want to manage the merges by hand you can maybe have two
>>>>> bsaelines?
>>>>> BaselineOfCalypso and BaselineOfCalypsoDev?
>>>>>
>>>>
>>>> It should work. But is it right way that everybody should follow?
>>>>
>>>> With configurations it was easy to do in single class.
>>>>
>>>>
>>>>>
>>>>> --
>>>>> Cyril Ferlicot
>>>>> https://ferlicot.fr
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> Guille Polito
>>>
>>> Research Engineer
>>>
>>> Centre de Recherche en Informatique, Signal et Automatique de Lille
>>>
>>> CRIStAL - UMR 9189
>>>
>>> French National Center for Scientific Research - *http://www.cnrs.fr
>>> <http://www.cnrs.fr>*
>>>
>>>
>>> *Web:* *http://guillep.github.io* <http://guillep.github.io>
>>>
>>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>>
>>
>>
>
>
> --
>
>
>
> Guille Polito
>
> Research Engineer
>
> Centre de Recherche en Informatique, Signal et Automatique de Lille
>
> CRIStAL - UMR 9189
>
> French National Center for Scientific Research - *http://www.cnrs.fr
> <http://www.cnrs.fr>*
>
>
> *Web:* *http://guillep.github.io* <http://guillep.github.io>
>
> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>
