Hello mentors, At the moment I am working on packaging "miktex-tools -- package manager for TeX" (ITP: Bug#481606 & Bug#481607). The original source file contains several libraries which are compiled into package libraries. However, most of the needed libraries appear to be already packaged in Debian. On http://people.debian.org/~daniel/documents/packaging.html#partial-sources I read that that fact could be reason to alter the upstream source file. My question is: should the source be "cleaned" from these library sources, or should that only be done when the build is against the actual Debian libraries? If it should be cleaned, how to cope with versions, as upstream might not update the library sources all the time? Furthermore, the upstream source is meant for a MS Windows program with lots more functionality than implemented in the tools for Linux, should the code/directories for that functionality be stripped? (Of course I could also ask upstream to do that next time but unfortunately upstream has not yet responded to even a previous question I asked). I do not know (yet) how to build the upstream source against those libraries from Debian (several are listed below) because the project is currently configure to create it's own libraries. The homepage of MiKTeX: http://www.miktex.org/unx/ Original source file: http://mirror.ctan.org/systems/win32/miktex/source/miktex-2.7.2960.tar.bz2 Debian package - current version in lenny (MiKTeX version uses) bzip2 1.0.5-0.1 (used: 1.0.4) libcurl3 7.18.1-1 (used 7.17.1) libexpat1 1.95.8-4 (used: 2.0.0) libgraphite3 1:2.2.1-2.1 (used 2.2.1 svn 812) p7zip-full 4.57~dfsg.1-1 (used: 4.57) zlib1g 1:1.2.3.3.dfsg-12 (used: 1.2.3) An addition unrelated question: is there a tool to scan through the files of a project to find the copyright/license of the files? This project has 5836 files and I don't like scanning them all manually :) With kind regards Paul Gevers
Attachment:
signature.asc
Description: OpenPGP digital signature