py-gobject3-common vs. py*-gobject3

[David Holland <dholland-pkgtech%netbsd.org@localhost>]

py-gobject3-common is equipped with a bl3 file (which is correct,
since the two files it installs are a C header and a pkgconfig file)
and py-gobject3 includes it to build. But, it sets BUILDLINK_DEPMETHOD
to "build". The net result of that is that neither the output
py*-gobject3 packages nor anything else depends on py-gobject3-common.

ISTM that:
 - either that header and/or the pkgconfig file are needed at runtime,
   in which case all py*-gobject3 packages should depend on
   py-gobject-common so it doesn't evaporate under them;
 - or they really are needed only at build time, in which case... why
   are they getting installed?

Now, the header file could go either way but it seems likely that
having the pkgconfig file missing at runtime would cause things to
break.

So, anyone object to me changing the BUILDLINK_DEPMETHOD back to full
and bumping py-gobject3?

-- 
David A. Holland
dholland%netbsd.org@localhost