Hi,
since I had been working on a doxygen port in parallel to Aleksander
Piotrowski, I am now busy revamping my port with things he did in his.
The result's supposed to be pretty sweet, but I need some feedback in
advance.
1. Doxygen documentation
There is a separate manual distribution tarball on doxygen.org, but it
only contains the manual in PDF format. Rebuilding the docs within the
port is not a problem per se, it's simply taking for ages and is a very
memory hungry process as well. The documentation (and accompanying
examples) shall go into a subpackage anyways, but which PSEUDO_FLAVOR do
you want? ``docs'' or ``no_docs''?
2. (Optional) dependencies
This part is related to 1., since the optional RUN_DEPENDS (which could
be left as a simple note in pkg/DESCR like in Aleksander's port) become
BUILD_DEPENDS for the documentation. Those include graphviz, teTeX and
ghostscript. The former is a PITA to install from ports, but okay when
installed as a package. The other two are either large, or add hidden
X11 dependencies(*) (unless they were specifically installed in their
respective no_x11 flavors beforehand) or both. What do you think about
specifically tagging them as RUN_DEPENDS for doxygen and being done with it?
3. Miscellaneous
There is an issue I haven't found a proper solution for, yet - when
building the doxygen documentation, the `dot' utility from the graphviz
package writes_to_HOME. Any hints on how to typically solve this kind of
stuff, or a confirmation that it doesn't matter would be highly
appreciated. My attempts at fiddling around with the HOME environment
variable, setting it to somewhere inside $WRKBLD or similar didn't
really work out.
Thanks for your input,
Moritz
*: AFAIR, port builders / people who use ports are supposed to have X11
installed, making this a no-problem.
