Package: dpkg-dev Version: 1.13.25 Severity: wishlist Debian source packages are hard to deal with when it comes to local modifications. Suppose I want to build a package with a custom patch applied. In theory it is supposed to work like this: run dpkg-source -x (or unpack an .orig.tar.gz and apply a .diff.gz), then apply the custom patch, then run dpkg-buildpackage.
It is not so easy in practice. The result of dpkg-source -x often consists of the original source (sometimes not even unpacked!) and patches that are applied during the build process. My custom patch should be applied after those Debian patches - otherwise they may just fail. There are all kinds of build systems in source packages - some are hand-crafted and some are automatic (like dbs and cdbs), and each must be hooked into in a unique way. To put it in short, I want the source code "in the preferred form for making modifications to it" (quoting the GPL), and debian source packages do not give me that. To allow modifications, the source should not be altered during the build process. I think the dpkg tools and policy can be improved to fix this. For example, there could be a standard, documented target like 'make-source' in debian/rules which produces real sources from the result of dpkg-source -x. Or, even less intrusive, there may be an optional script to that purpose with a special name under debian/. And some checker could verify that the resulting source files are not modified during the build. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
