No. There is an issue on the issue tracker.
If nobody pushes, nothing will happen.
Marcus
> On 20 Jul 2015, at 21:04, Peter Uhnák <[email protected]> wrote:
>
> Hi,
>
> I was playing around with metacello because I wanted to ignore warnings with
> locks...
>
> currently I am doing something like
>
> ~~~~~~~~
> Metacello new
> baseline: 'ProjectAAA';
> repository: 'gitfiletree:///path/to/projectAAA';
> lock.
>
> Metacello new
> baseline: 'ProjectBBB';
> repository: 'gitfiletree:///projectBBB';
> onConflict: [ :ex | ex allow ];
> load.
> ~~~~~~~~~
>
> This will load both projects via gitfiletree, however it will also generate a
> lots of lock warnings which I have to manually confirm - this is bad for
> scripts.
>
> So the docs (
> https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandReference.md
>
> <https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandReference.md>
> )
>
> mention onLock: [ :ex | ex honor ], however in Pharo 5.0 there is no such
> method "honor".
>
> Is this bug?
> Should Metacello be updated on Pharo 5.0?
> Will this even solve my problems? (Honoring locks while not throwing
> warnings).
>
> Thanks,
> Peter
