Re: py-gobject3, meson, and python versioning

[Juraj Lutter <otis%NetBSD.org@localhost>]

+1 for meson as a tool.

In this case, what would be the correct/preferred way to keep track of meson updates?

otis

—
Juraj Lutter
URL:  http://www.wilbury.sk/
XMPP: juraj%lutter.sk@localhost
Do not hesitate to inquiry for professional services!

> On 29 Sep 2019, at 13:04, Kamil Rytarowski <n54%gmx.com@localhost> wrote:
> 
> On 29.09.2019 12:41, nia wrote:
>> The latest py-gobject3 update broke the py27 version and a bunch of
>> dependent packages. This is because it now needs meson and pkgsrc can't
>> invoke meson when python2 is in use by the package - it's python3 only.
> 
> I landed into this myself and it blocked building pakcages for me.
> 
> meson should be treated like a tool.
> 
> Purging py2-gobject3 can happen independently.
>