https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291316

Charlie Li <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #267274|                            |maintainer-approval-
              Flags|                            |

--- Comment #44 from Charlie Li <[email protected]> ---
Comment on attachment 267274
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=267274
tarball with 4 git format-patch patches

LZMA support is removed, including that the configure flag no longer exists.

The upstream issue for removing -python
https://gitlab.gnome.org/GNOME/libxml2/-/issues/891 is still open. While this
can signify dissatisfaction in the bindings' continued presence, no firm action
has been taken by the current maintainers, so EXPIRATION_DATE is premature. Not
to mention one consumer still uses it unfortunately. At most DEPRECATED without
a date is fine.

The current upstream maintainer has completed work on the XPath stuff and is
now committed as
https://gitlab.gnome.org/GNOME/libxml2/-/commit/0e50b31902cdb1eb242eb361c123e9e033b2af87
; please use this commit directly (verified applies cleanly).

net/pacemaker2 currently does not have a port maintainer so not sure why it's
lumped in here, it could have been committed already. May also be a good idea
to split security/xmlsec1 into a separate PR for approval since it has not been
provided yet.

Not totally satisfied with this design of providing docs. For the value that
docs provides, it does not warrant a dance of flavours or child ports, unlike
the bootstrap method from devel/glib20 and devel/gobject-introspection. The
gtk-doc portion, ie the API documentation which are all HTML files, already
live online as https://gnome.pages.gitlab.gnome.org/libxml2/html/index.html ,
so while nice to have locally, is not a priority if it introduces unnecessary
complexity to build them. This leaves the man pages, which I'm more inclined to
take bapt@'s approach of pre-rendering them or use docbook2mdoc at build time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Reply via email to