* Moritz Grimm [2005-06-19]: > 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
Not a problem. > 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 Is it worth it? What other *useful* format does this bring us? > examples) shall go into a subpackage anyways, but which PSEUDO_FLAVOR do > you want? ``docs'' or ``no_docs''? The simple solution is to download the pdf and not add a PSEUDO_FLAVOR at all. For the complex case of building the documentation yourself, the rule of thumb is, that ports are there for package builders to build packages. Therefor I'd go with 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 Again, there's a simple solution to all this. :) > 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? I don't quite understand this. If they are optional, there's no reason to add them as RUN_DEPENDS. If doxygen is hardly useable w/o them, add them as RUN_DEPENDS as they are not really optional. If you build the documentation yourself, additionally add them as BUILD_DEPENDS. > 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 Doesn't matter. > appreciated. My attempts at fiddling around with the HOME environment > variable, setting it to somewhere inside $WRKBLD or similar didn't > really work out. Don't do this, dot might just want to update its config file or sth. As you already see the warning, everything is doing fine. If dot really wrote somewhere outside WRKDIR, that'd be bad. > *: AFAIR, port builders / people who use ports are supposed to have X11 > installed, making this a no-problem. Yes. Nikolay
