[Pharo-project] removing versions from configurations
tudor.girba at gmail.com
Mon Apr 25 19:37:29 CEST 2011
On 25 Apr 2011, at 18:50, Stéphane Ducasse wrote:
> Indeed but loading default could have destroyed your image.
> So RPackage should not be managed with default.
I do not understand. The continuous integration server is there to check these issues.
The correspondent would be to load now the current baseline. If that breaks, it breaks and people look at it.
Moose is now developed on multiple fronts and serves multiple interests that are not necessarily synchronized. So, we want to depend on latest things because this ensures communication and puts more pressure on synchronizing issues. This is why we want to play with the latest Pharo (hopefully, we will the development to it next week).
Every time we depend on something fixed, we introduce the difficulty of migrating to the next version.
> Now for stable I'm not sure that I set it up well so watch out.
The tests say that for the use of Moose, RPackage works Ok.
> On Apr 25, 2011, at 12:51 PM, Tudor Girba wrote:
>> The Moose build broke because the 'default' version was removed from ConfigurationOfRPackage.
>> I fixed it now by using #stable, but that is not the issue.
>> I understand the need for cleaning, but we should be aware that removing versions from configurations can have far reaching ripple effects.
>> "From an abstract enough point of view, any two things are similar."
"Don't give to get. Just give."
More information about the Pharo-project