On 02/03/2014 12:57 PM, Sebastien Jodogne wrote:
Hi Andreas,The problematic files are all *.js files since they are compressed and not to be considered as editable source files. Your task would be to verify, whether there are any *.js files just packaged for Debian (checkout files starting with libjs-* and apt-file search <file_in_question_perhaps_using_regexp_for_version_number.js> is your friend. You should strip these files from the upstream source. For this I'd recommend using "Files-Excluded" in debian/copyright (see `man uscan`). For those JS files that are not yet packaged I'd recommend to put the real uncompressed source into the dir debian/JS. To have some accepted example you might like to have a look into gnumed-client packaging: http://anonscm.debian.org/viewvc/debian-med/trunk/packages/gnumed-client/trunk/Thanks for this very helpful clarification. I have however an additional question: During the build process, all the Javascript/HTML/CSS/... resources are integrated into the Orthanc binaries. Is this behavior OK wrt. Debian guidelines?
BTW, another related question: How can I bring back the *.js/*.css files into the build folder, where the CMake build script expects them? Am I allowed to create symbolic links in the "override_dh_auto_configure" sections?
-- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
