On Mon, 2008-05-26 at 23:19 +0200, Paul Gevers wrote: > 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. Do you mean embedded source code? The source tarball containing identical / forked code from other upstream projects? > My question is: should the source be "cleaned" from these library > sources, Probably not. Other implementations may have different requirements. > 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? Upstream needs to support --disable-foo repeatedly for each component available elsewhere. Add those to your ./configure for example. > Furthermore, the upstream source is meant for a MS Windows program with > lots more functionality than implemented in the tools for Linux, Why? Licence problems? Missing dependencies? Debian looks for packages to have every option enabled that can be enabled. > 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. Then maybe the changes would be too widespread to able package it for Debian at all, at least until upstream see sense. > 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 :) licensecheck from devscripts. -- Neil Williams <codehelp@debian.org>
Attachment:
signature.asc
Description: This is a digitally signed message part