Re: Bug#736432: Fwd: Re: Bug#736432: [doxygen] Include header/footer/img as external ressource

Hi,

On Sun, 2014-02-02 at 20:04 +0100, Helmut Grohne wrote:
> Given that this report has not received sufficient information to
> warrant the patch tag I am turning the issue into what I believe is at
> its core: the embedding of jquery. It is already well documented at
> /usr/share/doc/doxygen/README.jquery. The issue obviously results from
> upstream decisions and I am not the one fixing it in the current
> ecosystem. That means the tag wontfix will stay until at least one of
> the following conditions is met:
>=20
>  * We can do Arch:all binNMUs.
>  * All relevant jquery auxiliary libraries are packaged and there is
>    commitment to packaging the future libraries Doxygen upstream will
>    introduce.
>  * There is a patch, that does not break legitimate use cases.
>=20
> Given that I am not doing the work, there are no tracker bugs for the
> former two issues. If they are created, I'd appreciate relevant block
> commands to the bts.
>=20
> Still hoping that I am wrong and things are easier than this. ;-)

Can someone explain the use of JQuery like I'm five to me? I'm asking becau=
se JQuery
requires "uglifyjs" which has a runtime dependency on NodeJS which heavily =
restricts
buildability of the reverse dependencies due to Google's unwillingness to p=
rovide a
generic, slow implementation of their V8 JavaScript engine. This limits the=
 whole
NodeJS stack to architectures with big companies behind as others don't hav=
e the funds
to support a V8 port.

>From what I understand, all that NodeJS does here is take some JavaScript c=
ode and
transpile it into other JavaScript code. I have never understood the purpos=
e of this
but Firefox suffers from the same problem [1] which makes the browser packa=
ge which
itself is very portable exclusive to release architectures.

On the other hand, the JavaScript files can also be "cross-transpiled" from=
 architectures
that have NodeJS support to architectures which don't. Oracle does this in =
Solaris allowing
them to build and ship Firefox for Solaris SPARC [2].

Wouldn't it be possible to do that here as well? Can't we just transpile th=
e JavaScript
on amd64 and stuff the result into the doxygen-common package?

FWIW, I was able to build the doxygen package on sparc64 without the uglify=
js build
dependency and after removing the call to jquery in debian/rules.

Adrian

> [1] https://buildd.debian.org/status/package.php?p=3Ddoxygen
> [2] https://github.com/oracle/solaris-userland/tree/master/components/des=
ktop/firefox/wrapper-node

--=20
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913