On Sat, Apr 30, 2016 at 5:14 PM, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Hi Peter,

Le 29/04/2016 18:22, Peter Uhnák a écrit :
Welp apparenty GitFileTree has already switched to OSSubprocess… which
means that since I use Moose I can no longer commit my code… which is
fun. -_-

For Pharo 5.0, I've pushed both #dev and #stable versions of GitFileTree which will reuse either OSProcess or OSSubprocess if it is already loaded and will avoid reloading OSSubprocess over OSProcess.

Could you try with Moose to see if it solves the problem you have? Just tell how it goes.

This indeed solves the Moose + Git problem, thanks!

Although the underlying problem still remains… which I don't understand, so I guess I will have to take a look to learn a bit.
Because imagine a year from now someone else comes along with a new library, or OS(Sub)Process goes through a backwards-incompatible rewrite into OS(Sub)Process2 and suddenly we are where we started...



Moose-dev mailing list