This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin Apps List <cygwin-apps at cygwin dot com>
- Date: Mon, 01 Oct 2012 19:27:39 -0600
- Subject: Re: [ITP] doxygen-1.8.0-2 -- A documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D.
- References: <50674A3B.4060801@tiscali.co.uk>
On 9/29/2012 1:21 PM, David Stacey wrote:
wget \
http://www.drstacey.talktalk.net/doxygen-1.8.0-2.tar.bz2 \
http://www.drstacey.talktalk.net/doxygen-1.8.0-2-src.tar.bz2 \
http://www.drstacey.talktalk.net/setup.hint \
http://www.drstacey.talktalk.net/md5.sum
You should keep using -1 for subsequent build attempts until one gets
RFU'd. Use new package versions only to disambiguate published package
versions. The package version number is there to help setup.exe out,
not to help us poor humans out. :)
Nits:
1. Another build requirement change: the doxygen.README file still
refers to TeTeX, which was replaced recently with TeX Live. But,
installing a basic TeX setup alone isn't enough. To build the PDF
manual, you need the optional texlive-collection-fontutils package for
epstopdf, and texlive-collection-latexextra for float.sty. There's no
need to mention any other packages. Installing those two into a stock
Cygwin install will drag in enough of the remaining TeX stuff to build
the manual.
2. /usr/share/doc/doxygen/latex should be removed, in favor of a .../pdf
subdirectory. I don't see a reason to ship source and intermediate
build files here, expecting the user to build the docs. What's wanted
here is a PDF of the LaTeX *output*.
3. I'd rather see your first version be 1.8.2-1 instead. Why start with
a version two bug fix releases back?
Nits aside, I can't withhold a GTG recommendation, since your packages
are no worse off than mine were, and those were apparently still useful
to people. :)
Something to pursue later, having no effect on GTG status:
There's a bogus test in Doxygen's configure script, where it goes
looking for dot(1) from GraphViz. It does a weak check for it in a few
common locations, and yells if it isn't there. dot(1) being a filter,
there isn't a huge penalty for using the native Windows version, which
of course doesn't get installed in any of those locations. It would be
nice to either 1) send upstream a test using the PATH instead of a
hardcoded list; or 2) adopt Yaakov's GraphViz package:
http://cygwin.com/ml/cygwin/2010-10/msg00232.html
Option 1 is sufficient, but option 2 means you can make graphviz a
dependency of your doxygen package, so everyone gets it automatically.