FreeBSD Bugzilla – Bug 190943
upgrade devel/doxygen 22.214.171.124 -> 1.8.7
Last modified: 2014-08-11 06:08:03 UTC
Created attachment 143688 [details]
svn diff for doxygen
libreoffice wants to use doxygen >= 1.8.4, so please check and approve.
poudriere build log see http://people.freebsd.org/~pi/misc/doxygen-1.8.7.log
Oh, I've been WANTING to update the port for ages now. But there is a small problem, while it builds you for in poudriere, that is with the default options, the port currently does NOT build if the option to build doxygen's PDF docs is enabled. Sadly, no one seems to know the solution to fix it, as it fails with both teTeX and TeX Live.
I'm willing to submit my own patch for it, but I need to get the PDF doc generation option working.
The mailing list thread I had started about it was here: http://lists.freebsd.org/pipermail/freebsd-ports/2014-March/090875.html
Granted, this might not seem like THAT big an issue, since the port can be usable without doxygen generating its own docs. But I believe this issue will cause even user invokation of doxygen to fail if they want PDF docs of their own code. I believe it had been said in the past that this option should not be removed from the port, despite the headaches it causes.
Created attachment 143759 [details]
patch with all options working
This patch provides 1.8.7 with all options working.
Two small open issues:
- The PDF generated does hot have the same depth of indention in chapter 28 (perl modules tree) that the HTML has.
- If you want PDF, you have to select HTML as well
It is achieved by patching the auto-generated latex/Makefile and the autogenerated latex/refman.tex before running both.
It also forces pdflatex to run non-stop and to ignore the resultcode. This
is a compromise (also known as ugly hack) due to latex sub-itemize-limits.
for some pointers to the issue (but no working solution).
We're trying to inform upstream about those issues and hope for feedback.
In the meantime I ask for approval to commit this update.
Link to the HTML version that shows additional indention:
Created attachment 143761 [details]
Alternate paching for Makefile and files/patch-md5
I'm mostly fine with the update. However, I am attaching my own patches for Makefile and files/patch-md5 (which you had split apart in your diff, and I'm fine with that).
The Makefile patch does not include the MAKE_JOBS_UNSAFE that your patch has, but it includes requiring flex from ports (as I was running into problems because of the older flex in the base for my 9.2 on here) and adding a few extra flags to CONFIGURE_ARGS, as well as using USE_PYTHON_BUILD instead of adding python to the BUILD_DEPENDS.
The files/patch-md5 patch is slightly different than before, because I included a few other places that should've also been patched to use the base MD5 implementation. If you wish to keep the MD5 patches split like in your patch, I'm fine with that, but I included it as I currently have it in my local edit of the port.
MAKE_JOBS_UNSAFE is needed, otherwise the build with PDF etc fails according to my tests.
Consolidating your patches now spoils a working commit 8-}
I suggest to commit now, and you provide separate patch-md5-parts and
the other Makefile patches in a new PR which I will work on tomorrow ?
Is that OK ?
Well, as long as the port builds for everyone else without my changes to the Makefile, I'm fine with that. The biggest reason for needing the ports version of flex is that building doxygen itself was failing for me because of the old base version of flex. Otherwise, go right ahead with the commit.
A commit references this bug:
Date: Sat Jun 14 07:22:57 UTC 2014
New revision: 357752
devel/doxygen: 126.96.36.199 -> 1.8.7
In a second step, the python build part has to be tested (still open)
Submitted by: Naram Qashat <firstname.lastname@example.org> (maintainer)
I just committed the change with some of your changes integrated.
The USE_PYTHON_BUILD change was left on the sidelines, because it breaks
It was tested in poudriere on 10.0 and 9.2 (both amd64), but only without the
options. I'll check that post-commit (yes, I know...)
Please re-submit those md5 changes I missed. For the md5 patches: if possible,
please do not provide one big patch-md5, but seperate files.
Created attachment 143785 [details]
Small Makefile and md5-related patch
OK, I'm attaching a patch that removes a line from the Makefile (a USE_PYTHON_BUILD line that was conditional) and also adding a single MD5-related patch, as all the others have been taken care of.
I reverted the upgrade from 188.8.131.52 to 1.8.7 because some ports broke,
as reported by antoine@ and because culot@ suggested doing so:
- devel/libdbusmenu-qt (413 skipped!)
https://phabric.freebsd.org/D228 was set up to review the fix for libdbusmenu-qt.
The issue open to discussion: does it require a exp-run and fix of
probably 100 ports to upgrade doxygen ?
Created attachment 145488 [details]
This is the current patch for others to test against.
(In reply to Kurt Jaeger from comment #10)
> The issue open to discussion: does it require a exp-run and fix of
> probably 100 ports to upgrade doxygen ?
The consensus was: Yes, exp-run is necessary. Preparing a patch that allows this.
> The consensus was: Yes, exp-run is necessary. Preparing a patch that allows
It's now at http://people.freebsd.org/~pi/misc/20140808-doxygen.svndiff
A commit references this bug:
Date: Sat Aug 9 19:39:12 UTC 2014
New revision: 364468
Update devel/doxygen to 1.8.7
Update dependent ports to build with it
Most of work by: pi@
OK, I know this was committed, but I have to question something in the patch to update it to 1.8.7. Why is there a forced dependency on print/tex-dvipsk and print/cm-super? The port doesn't need tex to build UNLESS the PDFDOCS option is enabled. And I have no idea why print/cm-super was added. Can this be looked in to? Especially the tex part, because someone apparently complained to me about the forced dependency on tex.