The proper upstream Python package name is pygobject; version 2
hasn't existed or been supported in ages, so rename.
Rework the port to where -common is the child port but the main
port depends on it for the header files. Build the main port as a
Python wheel USE_PYTHON=pep517 to take advantage of USE_PYTHON=autoplist.
Direct -common consumers have PORTREVISION bumped.
Changelog: https://gitlab.gnome.org/GNOME/pygobject/-/blob/3.50.0/NEWS
Reported by: Olivier Duchateau <duchateau.olivier[at]gmail[dot]com> (3.44, 3.46)
Exp-run by: antoine
PR: 273722
Differential Revision: https://reviews.freebsd.org/D47635
This is the FreeBSD Ports Collection. For an easy to use
WEB-based interface to it, please see:
https://ports.FreeBSD.org
For general information on the Ports Collection, please see the
FreeBSD Handbook ports section which is available from:
https://docs.freebsd.org/en/books/handbook/ports/
for the latest official version
or:
The ports(7) manual page (man ports).
These will explain how to use ports and packages.
If you would like to search for a port, you can do so easily by
saying (in /usr/ports):
make search name="<name>"
or:
make search key="<keyword>"
which will generate a list of all ports matching <name> or <keyword>.
make search also supports wildcards, such as:
make search name="gtk*"
For information about contributing to FreeBSD ports, please see the Porter's
Handbook, available at:
https://docs.freebsd.org/en/books/porters-handbook/
NOTE: This tree will GROW significantly in size during normal usage!
The distribution tar files can and do accumulate in /usr/ports/distfiles,
and the individual ports will also use up lots of space in their work
subdirectories unless you remember to "make clean" after you're done
building a given port. /usr/ports/distfiles can also be periodically
cleaned without ill-effect.