Hi,

Ok, that is a better reason.

As far as I can tell, the baseline situation is not much better, is it?

Cheers,
Doru



> On Apr 15, 2017, at 11:12 PM, Cyril Ferlicot D. <[email protected]> 
> wrote:
> 
> On 15/04/2017 23:08, Tudor Girba wrote:
>> Hi,
>> 
>> I do not quite understand the benefit of removing Configurations in Pharo 6. 
>> Is there a benefit that I do not see?
>> 
>> Cheers,
>> Doru
>> 
>> 
> 
> If you have a project depending on another project that got his
> configuration in the image, the configuration will not be updated if you
> do not do it explicitly.
> 
> We found with Pavel that the version of MooseAlgo used by Moose was
> outdated because ConfigurationOfMooseAlgos was in the image with 5-6
> commits late.
> 
> Users should not have to update the configuration of the dependencies of
> their project by hand in their builds because Pharo has old
> configurations inside the image.
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr
> 
> http://www.synectique.eu
> 2 rue Jacques Prévert 01,
> 59650 Villeneuve d'ascq France
> 

--
www.tudorgirba.com
www.feenk.com

"Yesterday is a fact.
 Tomorrow is a possibility.
 Today is a challenge."





Reply via email to