On 08/05/14, 08:01am, Daniel Baumann wrote: > src:lxc contains documentation (*.sgml only) and build-depends on > docbook2x, no jquery is needed or installed as build-depends. the > resulting bin:lxc-dev then contains a *compressed* jquery.js put there > by docbook2x. lintian detects this and warns about it (W: > embedded-javascript-library). > > i think we have the following possibilities to handle such embedding of > files by build-depends, where the embedded files were not part of the > original source (starting with least favourable one): > > A: ignore it and overwrite the lintian warning > > B: overwrite the lintian warning, use a built-using: relation in > control (in lxc case, against docbook2x which imports the > jquery.js) > > C: post-process the binary package content at buildtime to replace > the embedded files through proper depends (e.g. for jquery, > replace the file with a symlink to /usr/share/javascript/jquery > /jquery.js and have a depends or recommends on libjs-jquery). > > this could potentially have side effects if the copy of the > to-be-embedded file (jquery.js) inside the tool that imports it > (docbook2x) is not in sync with the standalone packaged version > (libjs-jquery), so that we end up with a newer/incompatible > version. > > for lxc, i'd go with C. > > did i miss anything? (yes, i haven't fully read the last thread about > jquery on debian-devel a couple of weeks ago, i think it only covered > the 'what to do with embedded js in source packages'-cases, not this > 'what to do with embedded js in binary packages not being part of the > source package'-case).
I actually think there's a D option and is based on the solution that Daniel Kahn Gillmor gave on a similar issue I had with powertop, which is using native javascript instead of jquery. [0] Of course, this wouldn't be on lxc but directly on docbook2x and that would fix it for more packages than only lxc. [0] https://bugs.debian.org/695890 Other people in this thread has already pointed out the issues with several versions of jQuery and I honestly believe native javascript should be enough for the transformations docbook2x seems to be using. BTW, I failed to see on docbook2x website how is that javascript is used at all. Would you give me a hint so I don't need to build the package myself to check if this is actually a viable solution in this case as well? Kind regards. -- Jose Luis Rivas | ghostbar The Debian Project → <http://www.debian.org> GPG 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140508130217.gb1...@arya.ghostbar.co
