Helmut Grohne | 26 Feb 22:30 2013
Picon

jquery embedding in doxygen

Dear javascript maintainers,

I am writing to you, because I seek help with doxygen. For wheezy I
believe that Mònica Ramírez Arceda's patch is the way to go, so this
mail entirely applies to jessie.

** First embedding of jquery: src:doxygen

The current situation is that doxygen upstream downloads various parts
of jquery in various versions, then obfuscates (or is it called
"compresses"?) the source and stores those parts in their svn. Then they
convert the jquery library into a C header file which is also stored in
their svn. The lack of source for jquery in the sense of "preferred form
for modification" is tracked as #625956. According to upstream svn these
copies are usually generated immediately before releasing a new version
of doxygen.

** Second embedding of jquery: doxygen

The header is compiled to the doxygen binary, so the binary package also
includes a copy of jquery. Once you generate documentation this version
is copied to your documentation tree.

** Third embedding of jquery: reverse build dependencies of doxygen

About 50 packages use doxygen to build their documentation. Unless the
maintainer explicitly replaces the doxygen generated copy of jquery, the
respective package includes it as well.

** So precisely what is copied?
(Continue reading)

Jonas Smedegaard | 27 Feb 00:22 2013
Picon

Bug#625956: [Pkg-javascript-devel] jquery embedding in doxygen

Quoting Helmut Grohne (2013-02-26 22:30:00)
> ** First embedding of jquery: src:doxygen
> 
> The current situation is that doxygen upstream downloads various parts 
> of jquery in various versions, then obfuscates (or is it called 
> "compresses"?) the source and stores those parts in their svn. Then 
> they convert the jquery library into a C header file which is also 
> stored in their svn. The lack of source for jquery in the sense of 
> "preferred form for modification" is tracked as #625956. According to 
> upstream svn these copies are usually generated immediately before 
> releasing a new version of doxygen.

I believe the Debian packaging should ignore the prebuild stuff shipped 
by upstream, and during the Debian build mimic same steps as done 
upstream but build-depending on and using Debian-packaged jquery files 
(either uncompressed or compressed - but most likely the best result 
comes from joining all needed files uncompressed and compress them all 
at once).

> ** Second embedding of jquery: doxygen
> 
> The header is compiled to the doxygen binary, so the binary package 
> also includes a copy of jquery. Once you generate documentation this 
> version is copied to your documentation tree.

Ideally doxygen should be patched to not work like that but instead at 
runtime use the Debian-packaged files (then also solving above first 
embedding of jquery).

Assuming that is too difficult, I would suggest do a dirty trick of 
(Continue reading)

Jonas Smedegaard | 27 Feb 00:22 2013
Picon

Bug#625956: [Pkg-javascript-devel] jquery embedding in doxygen

Quoting Helmut Grohne (2013-02-26 22:30:00)
> ** First embedding of jquery: src:doxygen
> 
> The current situation is that doxygen upstream downloads various parts 
> of jquery in various versions, then obfuscates (or is it called 
> "compresses"?) the source and stores those parts in their svn. Then 
> they convert the jquery library into a C header file which is also 
> stored in their svn. The lack of source for jquery in the sense of 
> "preferred form for modification" is tracked as #625956. According to 
> upstream svn these copies are usually generated immediately before 
> releasing a new version of doxygen.

I believe the Debian packaging should ignore the prebuild stuff shipped 
by upstream, and during the Debian build mimic same steps as done 
upstream but build-depending on and using Debian-packaged jquery files 
(either uncompressed or compressed - but most likely the best result 
comes from joining all needed files uncompressed and compress them all 
at once).

> ** Second embedding of jquery: doxygen
> 
> The header is compiled to the doxygen binary, so the binary package 
> also includes a copy of jquery. Once you generate documentation this 
> version is copied to your documentation tree.

Ideally doxygen should be patched to not work like that but instead at 
runtime use the Debian-packaged files (then also solving above first 
embedding of jquery).

Assuming that is too difficult, I would suggest do a dirty trick of 
(Continue reading)


Gmane