(Please reply to list as well thanks) 2009/9/3 Alessandro Dentella <san...@e-den.it>: >> > Last question >> > ------------- >> > >> > When testing creating the package from my newly created sources on a newer >> > machine (ubuntu 9.04), lintian complained: >> > >> > W: python-sqlkit: embedded-javascript-library >> > usr/share/doc/python-sqlkit/html/_static/jquery.js >> > >> > That's clearly the jquery of the sphinx documentation. It's introduced in >> > the upstream package when sphinx compile the docs (not at my build time). >> > >> > Is it mecessary to fix this or I can just leave it as is (it appears as a >> > warning, not an error). >> > >> >> Imho documentation should be build (rebuild) at deb package building stage. > > What's the advantage? > > * it's html text > * would be just as the one shipped in the upstream version > * it would still put jquery.js in it as an automatic routing of sphinx > so I should anyhow decide what to do with it > > sandro > *:-) >
Think of html as binary and code/documentation as source. By rebuilding you will make sure that: 1) It's up to date 2) That htmls were not modified 3) The source works and produces correct documentation You should ship upstream "binaries" or html documentation because it's not the source (preferred form of modification). And think about the case when later you gonna apply a patch to the package you would want it to make it into documentation. Source+patches should match to produced documentation. I have no clue about the js file bit though. Remove it (via patch) and symlink it from the shipped package by debian? That is my wild guess. Or maybe contact sphinx maintainer in Debian. I hope there is an option to symlink it. > > -- > Sandro Dentella *:-) > http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy > -- With best regards Dmitrijs Ledkovs (for short Dima), Ледков Дмитрий Юрьевич -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
