Re: release tarballs

Hi Helmut,

On Apr 6, 2013, at 12:45 , Helmut Grohne <[email protected]> wrote:

> Dear Doxygen developers,
> 
> I am writing to you on behalf of the Debian project. There are a few
> issues with the doxygen package as shipped by Debian that are imho best
> addressed upstream. Please have a look at whether this is reasonable.
> 
> In http://bugs.debian.org/569504 Jonathan Nieder asked to include
> upstream changelogs and notes that these are only available from the
> website. Would it be possible to include changelogs in future release
> tarballs?

Yes, that possible. I'll make the changelog part of the HTML version of the manual.

> 
> The current way of shipping jquery in Doxygen poses a set of problems
> (mainly http://bugs.debian.org/625956) to Debian. In order to ship a
> package in the Debian main distribution the source code must be
> available in preferred form for modification. This is not the case with
> the version of jquery embedded in Doxygen tarballs, because they are
> minified. Would it be possible to additionally ship the original
> uncompressed javascript components in future release tarballs even if
> they are not used for building Doxygen?

Yes, I've compiled a package (see attachment) which I plan to include 
in the next release. It includes the non-minified scripts and a Makefile to 
compile them into the minified files that in turn can be compiled into doxygen.
Let me know if this meets the requirements. This approach also makes it 
relatively simple to try out newer versions of the scripts.



> 
> (Moving to wishlist stuff.)
> 
> In addition it would be great to be able to use the system version
> jquery instead of Doxygen's copy. It is not clear how to achieve this in
> a way, that does not pose unreasonable burden on either upstream or the
> Debian packaging. Discussion on this issue has started on
> http://bugs.debian.org/630982 but has not come to a final conclusion.
> The question relevant here appears to be whether Doxygen upstream could
> document which versions of jquery (+ components) it needs to work
> properly.

It is very difficult for me to validate and test multiple versions, that's why I 
included the files in doxygen. Not all jquery extensions used by doxygen work with
any jquery version. The generated jquery.js also contains more or less
extensions depending on the configuration.

> It would be interesting to know whether the javascript components, style
> sheets and icons shipped with one version of Doxygen could be used with
> an older version of Doxygen (possibly broken with major releases). That
> would allow us to move them to a package shared among documentation
> packages instead of having about 100 packages contain these copies. To
> get a rough idea on how many copies we currently ship, have a look at
> just the copies of the latest (packaged) version of doxygen.css:
> http://dedup.debian.net/hash/sha512/d43d1384010e768003ad5784c9a6af464046871f194dd069b7276aa06c9d96f5dbb9d6bc1faabe836c7713de9db31c54332803986d018f84c0856b410c597f74

So far this has proven not to be the case. I find it too restrictive and too hard to test 
if I would be forced to keep backward compatibility on the style and scripting files.

Regards,
  Dimitri

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html

_______________________________________________
Doxygen-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-develop