|author||Ian Jackson <email@example.com>||2017-01-09 03:04:13 +0000|
|committer||Ian Jackson <firstname.lastname@example.org>||2017-01-09 13:08:32 +0000|
dgit(7): Move autotools deletion para up
Signed-off-by: Ian Jackson <email@example.com>
1 files changed, 11 insertions, 11 deletions
@@ -282,6 +282,17 @@ branches, it will fail.
As the maintainer you therefore have the following options:
+Delete the files from your git branches,
+and your Debian source packages,
+and carry the deletion as a delta from upstream.
+(With `3.0 (quilt)' this means represeting the deletions as patches.
+You may need to pass --include-removal to dpkg-source --commit,
+or pass corresponding options to other tools.)
+This can make the Debian
+source package less useful for people without Debian build
Persuade upstream that the source code in their git history and the
source they ship as tarballs should be identical. Of course simply
removing the files from the tarball may make the tarball hard for
@@ -292,17 +303,6 @@ files, perhaps with some simple automation to deal with conflicts and
spurious changes. This has the advantage that someone who clones
the git repository finds the program just as easy to build as someone
who uses the tarball.
-Delete the files from your git branches,
-and your Debian source packages,
-and carry the deletion as a delta from upstream.
-(With `3.0 (quilt)' this means represeting the deletions as patches.
-You may need to pass --include-removal to dpkg-source --commit,
-or pass corresponding options to other tools.)
-This can make the Debian
-source package less useful for people without Debian build
Of course it may also be that the differences are due to build system
bugs, which cause unintended files to end up in the source package.