On Fri, Sep 4, 2015 at 11:49 AM, stephan <stephan@stack.nl> wrote:


On 04-09-15 11:42, Usman Bhatti wrote:
A new version only will not solve the problem. The fix also needs to be committed somewhere and if I commit the fix it in the main branch (see screenshot below), I need to merge all the the changes done for Moose 6.0 (and update other packages that these packages depend on) and hence break my tools in Moose 5.1.
Why? The only thing you are depending on is that #bleedingEdge returns a version for Moose 6, isn't it?

No. We are using the stable version of Moose (release Moose 5.1) for Pharo 4.0 and not the bleeding edge.


Stephan
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev