Re: pkg/59864: fonts/harfbuzz: Documentation build fails due to missing docbook-xsl and XML catalog

The following reply was made to PR pkg/59864; it has been noted by GNATS.

From: Mike Volokhov <[email protected]>
To: [email protected]
Cc: [email protected],
 [email protected],
 [email protected]
Subject: Re: pkg/59864: fonts/harfbuzz: Documentation build fails due to
 missing docbook-xsl and XML catalog
Date: Wed, 7 Jan 2026 04:05:46 +0200

 Hi!
 
 Well, it's hard to tell. The difference is at least in the Darwin
 and pkgsrc versions. I've recently updated it to pkgsrc-2025Q4 and
 did very fresh bootstrap, but the issue remains in the place.
 
 IMHO it is not a local environment issue, but rather that the pkgsrc
 xsltproc binary does not load the system XML catalog by default (should
 it tho?).
 
 The gtk-doc is correctly configured to use the pkgsrc binary:
 
 $ grep xslt /opt/pkg/share/gtk-doc/python/gtkdoc/config_data.py
 xsltproc = '/opt/pkg/bin/xsltproc'
 
 When running that binary with verbose output, it shows it does not
 load the catalog automatically:
 
 $ echo "<doc/>" | /opt/pkg/bin/xsltproc -v - 2>&1 | grep catalog
 (no output, error code 1)
 
 Because xsltproc is blind to the local catalog, it attempts to fetch
 the stylesheets from sourceforge.net <http://sourceforge.net/> and fails.
 
 My proposed "fix" works because explicitly exporting XML_CATALOG_FILES
 forces xsltproc to look in the right place, bypassing the network check.
 
 Since gtk-doc relies on xsltproc, harfbuzz (and potentially other
 packages using gtk-doc) should probably ensure XML_CATALOG_FILES is
 set in the MAKE_ENV to prevent this network dependency. Or xsltproc
 should be enforced to the default catalog at /opt/pkg/etc/xml/catalog.
 
 --
 Mishka