Re: what if upstream provides debian build directory
Adam Borowski <kilobyte@angband.pl> writes:
> The 3.0 format has a number of upsides and one downside: quilt. Sadly,
> the variants are only 3.0 (native) which doesn't apply and 3.0 (quilt).
> The latter interacts disastrously with keeping the packaging under
> version control -- and the very idea of _not_ using version control
> today is quite ridiculous.
> But fortunately it's simple to turn 3.0 (quilt) into 3.0 (sane): adding
> "rm -rf .pc debian/patches" to the "clean" rule gives you something
> that's effectively 1.0 format with all the goodies of 3.0.
Much more reliable and simpler: Put "single-debian-patch" in
debian/source/options and then stick something like the following in
debian/source/patch-header:
| Subject: Collected Debian patches for <package>
| Author: <maintainer>
|
| The packaging for <package> is maintained in Git using multiple
| branches for fixes, which makes it complex to separate the changes easily
| into individual patches. They are therefore all included in a single
| Debian patch.
|
| For full commit history and separated commits, see the packaging Git
| repository.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: