This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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.

On 10/2/2012 1:10 PM, David Stacey wrote:
On 02/10/12 02:27, Warren Young wrote:
You should keep using -1 for subsequent build attempts
Apologies for that. I was following the advice here:

I was sure I'd seen Corinna complain about a -1 to -2 during a similar discussion over a proposed package upload, but even if my recollection is correct, I think the public document takes precedence.

2. /usr/share/doc/doxygen/latex should be removed,

I agree completely, but I kept the 'latex' directory for a couple of reasons. Firstly, this was consistent with the previous build of doxygen (1.7.4-1), which included the latex directory [1].

Yes, I realize you were just following my previous example, but I'm far from infallible. I saw something in your package I would have removed from mine if I'd realized that at the time.

Secondly, I rather
thought that if 'make install' wanted to install the latex directory
then it wasn't really my place to delete of it.

That's a much stronger argument.

You might ask on the Doxygen mailing list why they think Joe User wants the LaTeX manual sources installed. It might be something they've overlooked in their build system.

However, I've had a little look at a couple of popular Linux
distributions, and neither Fedora [2] nor Ubuntu [3] include the latex
directory in their doxygen packages.

Ditto RHEL.

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

If the configure script doesn't detect dot(1) then it isn't the end of the world - you can specify the location of the dot executable by specifying DOT_PATH in the project configuration file:

Are you sure Doxygen doesn't use dot during the package build process, such as part of building Doxygen's own manual? I don't see why it would bother trying to find it at configure time otherwise.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]