25 Sep
2015
25 Sep
'15
12:26 a.m.
On 24-09-15 21:33, phil(a)highoctane.be wrote:
Pharo is very stable. Running in production without
problems.
It takes a while to get things working on a new version of course.
Pharo4.0 is out since just a couple of months, of course all packages
aren't aligned.
I am using Pharo3.0 for commercial solutions and Pharo5.x for learning.
But you are right that configurations have to be rock solid.
I've found that #stable may not be so #stable and that it would be better
to load '1.2.3' instead.
The issue is that some dependencies are on #stable or similar symbols that
change and are giving headaches.
NO. The problem is that the dependencies are specified as numbered versions
instead of symbolic ones. That means that every change to a leave breaks
all configurations above. That is what creates the brittleness, not the
change itself.
Why are GlamourCore and therefore Roassal2 depending on broken versions
of Rubric?
Stephan