Package: dpkg-dev Version: 1.16.10 Severity: wishlist Hi,
Before the 3.0 formats came out, there were several patch system thingies that used similar concepts of having a debian/patches directory in which individual patches were stored. I never touched the things, because the packages I maintain are all fairly trivial (from a packaging POV, at least), and I just never saw the need for the added complexity of having to maintain patches in individual files and having to do all kinds of extra things before I can properly build a package. For this reason, I've never switched to the 3.0 (quilt) format, because it introduces the same kind of unnecessary complexity. Recently, however, I learned about the single-debian-patch option, and went ahead and tried it out on one of my packages. As I wrote in my blog, however[1], I then found that there are still more things that dpkg-source decides to do differently from the 1.0 formats. I don't buy the argument that splitting off patches into separate files makes it easier for me to communicate with upstream. I store all my upstream code and debian packaging data in a git repository; this allows me to retain the same amount of detail on whatever patches I apply to my packages (so I can just run "git diff debian..master $(ls | grep -v debian)" to find still-relevant patches), but has the benefit of providing more history on a patch (e.g., if a patch changes over the years, you can see that in a VCS but not in a simple file). I do however buy the argument that having a patch system makes it easier for downstreams to change my packages (they just need to add a file to debian/patches and be done with it). So I do want to change. I just don't want to change my workflow. Not one bit. Please document how to make dpkg-source behave exactly the same way for a 3.0 (quilt) package as it does for 1.0 non-native packages, so that those of us who actually like the 1.0 workflow don't have to go search for the right options to use by trial and error. Thanks, [1] http://grep.be/blog/en/computer/debian/3.0_source_formats -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-1-amd64 (SMP w/4 CPU cores) Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg-dev depends on: ii base-files 7.2 ii binutils 2.22-8 ii bzip2 1.0.6-4 ii libdpkg-perl 1.16.10 ii make 3.81-8.2 ii patch 2.6.1-3 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages dpkg-dev recommends: ii build-essential 11.6 ii clang-3.2 [c-compiler] 1:3.2repack-6 ii fakeroot 1.19-2 ii gcc [c-compiler] 4:4.7.2-1 ii gcc-4.4 [c-compiler] 4.4.7-4 ii gcc-4.6 [c-compiler] 4.6.4-2 ii gcc-4.7 [c-compiler] 4.7.3-4 ii gnupg 1.4.12-7 ii gpgv 1.4.12-7 pn libalgorithm-merge-perl <none> Versions of packages dpkg-dev suggests: ii debian-keyring 2013.04.21 -- no debconf information -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
