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

sebastic-guest pushed a commit to branch master
in repository website.

commit 418e7e61e301ebc302b9501efdf729ac9cb616d3
Author: Bas Couwenberg <sebas...@xs4all.nl>
Date:   Sat Feb 15 02:24:37 2014 +0100

    Expand 'Working with existing packages' section.
---
 policy.xml | 44 ++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 42 insertions(+), 2 deletions(-)

diff --git a/policy.xml b/policy.xml
index cf527c8..6448d72 100644
--- a/policy.xml
+++ b/policy.xml
@@ -822,11 +822,51 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, 
/usr/sbin/cowbuilder
             When the package is already in the Debian archive, you can use the
             <command>debcheckout</command> command with its
             <option>--git-track='*'</option> option.
+<programlisting>
+<command>debcheckout</command> <option>--git-track='*'</option> 
<replaceable>&lt;package&gt;</replaceable>
+</programlisting>
           </para>
           <para>
             To update the <literal>master</literal>, 
<literal>upstream</literal>
-            and <literal>pristine-tar</literal> branches at once, use the
-            <command>gbp-pull</command> command.
+            and <literal>pristine-tar</literal> branches from an existing clone
+            at once, use the <command>gbp-pull</command> command.
+<programlisting>
+<command>gbp-pull</command> <option>--prinstine-tar</option>
+</programlisting>
+          </para>
+          <para>
+            Make the changes to your package using the various
+            <link linkend="git-tools">tools</link> at your disposal.
+          </para>
+          <para>
+            Commit the changes in your git repository following the
+            <link linkend="git-commit-policy">Commit policy</link>.
+          </para>
+          <para>
+            And don't be afraid to
+            <ulink 
url="http://git-scm.com/book/en/Git-Branching-Rebasing";>rebase</ulink>
+            your local branches into coherent commits before
+            <link linkend="git-push">pushing your changes to 
git.debian.org</link>.
+          </para>
+          <para>
+            While working on your changes you like need to perform multiple
+            <link linkend="git-build-package">rebuilds</link> of the package.
+          </para>
+          <para>
+            Since the overhead of setting up the build environment can be quite
+            extensive when many build dependencies need to be installed,
+            it can be tempting to build the package with plain
+            <command>debuild</command> instead of using a clean
+            <command>cowbuilder</command> chroot.
+          </para>
+          <para>
+            It is highly recommended to always build the package in a clean
+            chroot using
+            <command>git-buildpackage</command> 
<option>--git-pbuilder</option>.
+            Refer to
+            <link linkend="git-pbuilder">Setup the build environment</link>
+            for details about creating the <command>cowbuilder</command>
+            chroots.
           </para>
           <para>
             ...

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

_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to