Thorsten Glaser <t...@debian.org> writes: > Ian Jackson dixit: >> The problem is that `3.0 (quilt)' has both advantages (eg that >> `nativeness' is declared explicitly) and disadvantages (patches stored
> Not necessarily: > | $ cat rs/debian/source/local-options > |single-debian-patch > | $ cat rs/debian/source/local-patch-header > |Please review changes against upstream code using SCM, > |see the Vcs-* tags in debian/control for its location. > | > (empty line at the end) > This allows working with 3.0 (quilt) packages precisely the same way > (well plus a “git clean -dfx” after building) than with 1.0 packages. local-options means that the maintainer sees a very different view of the package than any other consumer on the package via the archive. Not only is this philosophically a bit weird, it also breaks tools that try to keep the repository and maintainer view consistent (such as dgit). I suspect it is therefore not the solution Ian is looking for. -- Russ Allbery (r...@debian.org) <https://www.eyrie.org/~eagle/>