On Fri, Nov 23, 2012 at 12:01:05PM -0800, Russ Allbery wrote:
For right now, I think the best thing for the Doxygen *clients* to do is
just ignore this issue. It may need a bug against doxygen, though (and
possibly some help for the Doxygen maintainer).
I'm just wild-guessing that the new
On Fri, 2012-11-23 at 12:01 -0800, Russ Allbery wrote:
P.S: The above isn't an approval for embedding yet another version of
jquery in your package, I think it should be avoided as well if
possible. Probably one of the options is to patch upstream source code
so that it can work with the
Dear all,
I'm currently staring with packaging some software (initially intended
for debian-med) and amongst these packages is a software library with
its Doxygen created documentation.
Doxygen created a jquery.js script that depends somehow on the options
used to run the document creation
On 11/24/2012 01:54 AM, Gert Wollny wrote:
Now I've seen that Doxgen has the jquery-1.3.2.js file in the debian/
directory and in fact with this script the pages display correctly. My
question is now, should I also include this source file in the source
distribution, or would it suffice to
Thomas Goirand z...@debian.org writes:
On 11/24/2012 01:54 AM, Gert Wollny wrote:
Now I've seen that Doxgen has the jquery-1.3.2.js file in the debian/
directory and in fact with this script the pages display correctly. My
question is now, should I also include this source file in the source
5 matches
Mail list logo
