Bug 258507 - textproc/htmldoc: update to 1.9.12
Summary: textproc/htmldoc: update to 1.9.12
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL: https://www.msweet.org/blog/2021-05-1...
Keywords: patch
Depends on:
Reported: 2021-09-14 21:13 UTC by Robert Clausecker
Modified: 2021-09-15 22:43 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (jose)

textproc/htmldoc: update to 1.9.12 (2.93 KB, patch)
2021-09-14 21:13 UTC, Robert Clausecker
fuz: maintainer-approval? (jose)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Clausecker 2021-09-14 21:13:06 UTC
Created attachment 227906 [details]
textproc/htmldoc: update to 1.9.12

Update textproc/htmldoc to 1.9.12



While we are at it:

 - fix a wrong line break in USES that lead to wrong X11 use
 - move USE=jpeg back to being mandatory because it appears to be
   needed even if HTMLDOCGUI is off
 - make pkgconfig unconditional because it is needed even if
   gnutls is not used
 - remove arm64 pre-build as it doesn't seem to be needed (perhaps
   ndowens knows more; he added it)
 - remove a PPC patch by pkubaj as it no longer applies.  Please
   check if the port still builds on PPC.

Tested with Poudriere on armv7 arm64 i386 amd64 FreeBSD 13.0-RELEASE.

Maintainer appears to be unresponsive and has not replied to previous PRs about this port (e.g. bug #237515, bug #223721, and others; actually the last one were the maintainer responded was bug #106715 from 2006).  Am willing to take over maintainership if desired.
Comment 1 Daniel Engberg freebsd_committer 2021-09-15 21:30:13 UTC
Thanks, does upstream release archive work?
Looks good otherwise
Comment 2 Robert Clausecker 2021-09-15 22:29:23 UTC
(In reply to Daniel Engberg from comment #1)

The official release tarballs differ in that they do not ship the testsuite.  While the test suite is not currently hooked up or installed, it might be interesting to do so in a future update.  And there's no point in changing to a different release tarball and then later back.
Comment 3 Robert Clausecker 2021-09-15 22:43:11 UTC
Actually scratch that.  The testsuite is in .gitattributes as “export-ignore” so it is not in the github provided tarball.  The two actually have character by character identical files.  So no point in changing that either.