[Pkg-mongodb-maintainers] [pkg-mongodb] 243/394: debian/README.source: Be more descriptive on the workflow.

[Apollon Oikonomopoulos]

This is an automated email from the git hooks/post-receive script.

apoikos pushed a commit to branch master
in repository pkg-mongodb.

commit df784a3241cd04add1e922f3896a1068df293b57
Author: Rogério Brito <rbrito at ime.usp.br>
Date:   Fri Apr 12 22:27:24 2013 -0300

    debian/README.source: Be more descriptive on the workflow.
---
 debian/README.source | 27 ++++++++++++++++++++-------
 1 file changed, 20 insertions(+), 7 deletions(-)

diff --git a/debian/README.source b/debian/README.source
index f57974e..f4092f1 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -1,13 +1,26 @@
-gbp
-===
+git-buildpackage
+================
 
-Use of git-import-orig is highly encouraged.
+Use of the command `git-import-orig` from the git-buildpackage suite of
+scripts is highly encouraged, as it makes for an easier maintenance of the
+packaging.
+
+When importing new upstream versions, it is recommended to run:
+
+    git-buildpackage --pristine-tar --uscan
+
+so that most of the tasks are automated.
 
 
 debian/gbp.conf
 ===============
 
-debian/* files from upstream tarball are filtered out because the merge is really
-difficult to maintain.
-It is up to the maintainer to check manually for upstream changes in debian dir,
-especially man pages.
+The `debian/*` files from the upstream tarball are filtered out (read:
+"mostly ignored") because of divergences that create conflicts that are
+difficult to merge.
+
+That being said, it is a good thing to manually check what upstream changed
+in their `debian` dir and adapt those changes to the Debian packaging, as
+they may have changed build dependencies or other assumptions.
+
+ -- Rogério Brito <rbrito at ime.usp.br>, Fri, 12 Apr 2013 22:26:07 -0300

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-mongodb/pkg-mongodb.git