pkg/58997: devel/glib2 ships python script gtester-report but doesn't depend on python

[campbell+netbsd%mumble.net@localhost]

>Number:         58997
>Category:       pkg
>Synopsis:       devel/glib2 ships python script gtester-report but doesn't depend on python
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 15 15:25:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        
>Organization:
The GnetBSD Foundpython
>Environment:
>Description:
The devel/glib2 package ships an executable bin/gtester-report which starts with, e.g.:

#! /usr/pkg/bin/python3.12

However, the package doesn't depend on Python at run-time, so after installing this glib2 package, bin/gtester-report is non-functional.

For cross-builds, if LOCALBASE does not match CROSS_LOCALBASE, this trips check-interpreter.

For example, if you're building cross packages into /opt/pkg on a development/build machine with native packages in /home/user/pkg, there will be a _native build-time_ Python interpreter at /home/user/pkg/bin/python3.12, but the path that gets baked into gtester-report is /opt/pkg/bin/python3.12, which probably doesn't exist on the build machine -- or if it does by accident, it falsely pacifies check-interpreter.
>How-To-Repeat:
1. install a glib2 binary package but not python
2. run gtester-report

or

1. set up a cross-build with LOCALBASE != CROSS_LOCALBASE
2. build devel/glib2
>Fix:
Several options:

1. Make glib2 depend on Python at runtime.
   => Probably not desirable.

2. Split bin/gtester-report into a separate package, say devel/glib2-gtester, and don't include it in glib2.
   => Simple matter of programming, may require finding affected downstream packages (annoying) and adjusting them (easy).

3. Ditch bin/gtester-report altogether.  It has this comment at the top:

   # Deprecated: Since GLib 2.62, gtester and gtester-report have been deprecated
   # in favour of TAP.

   => According to https://gitlab.gnome.org/GNOME/glib/-/releases/2.62.0, glib2 2.62 dates from 2019-09-05, more than five years ago.  No idea how many things still use it that also still work with newer glib2.