2017-04-14 12:52 GMT+02:00 Andrei Chis <chisvasileand...@gmail.com>: > Isn't it a bit too late for such a change? Might break projects that > expect configurations to be present. >
I do not think so. We do not have configurations for the system itself (well, we have them in an external repository but they are not update since switch to baselines). They are used only for the actively maintained semi-external projects like GT, QA, Epicea, Zinc etc. However even in that case they are sometimes out-of-sync with the upstream. Most users of such configurations are using the upstream configurations. If some one is using wrongly the versions in Pharo, he uses reference to the Pharo repository where the configurations will still be present. Cheers, -- Pavel > > Cheers, > Andrei > > On Fri, Apr 14, 2017 at 1:07 PM, Pavel Krivanek <pavel.kriva...@gmail.com> > wrote: > >> Hi, >> >> in Pharo 7 all configurations will be removed and replaced with the >> baselines. The bootstrapped image itself does not load the configurations >> at all. Most of them is now outdated and old versions of configurations in >> the standard Pharo image can cause problems for users of newer versions >> semi-internal packages (like Moose-Algos). >> >> So we, me and Cyril think that we should remove all current >> Configurations from the image just before the Pharo 6 release. Do you see >> any disadvantages of this step? >> >> Cheers, >> -- Pavel >> > >
