aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorGuido Guenther <agx@sigxcpu.org>2007-10-03 13:32:41 +0200
committerGuido Guenther <agx@sigxcpu.org>2007-10-03 13:32:41 +0200
commit1ff242981d8c495454c4ad8bd7e2efbfc3cdc1d3 (patch)
tree00e53f65decf166e10115f23df20486bc099d82f /docs
parent4cc5697447675ddbeccddc4394ddb62fa27ddf17 (diff)
short paragraph on hacking on arbitrary debian packages
Diffstat (limited to 'docs')
-rw-r--r--docs/chapters/special.sgml25
1 files changed, 25 insertions, 0 deletions
diff --git a/docs/chapters/special.sgml b/docs/chapters/special.sgml
index b7982be..3ac7a80 100644
--- a/docs/chapters/special.sgml
+++ b/docs/chapters/special.sgml
@@ -101,4 +101,29 @@ builder = /usr/local/bin/git-pbuilder
put this into <filename>.git/gbp.conf</filename> in one of your &git; repositories.
</para>
+ <sect1 id="gbp.special.hacking">
+ <title>Working on random packages</title>
+ <para>
+ Whenever you need to work on an arbitrary Debian package you can check it
+ right into &git;:
+<programlisting>
+apt-get source --download-only <filename>package</filename>
+git-import-dsc <filename>package</filename>*.dsc
+cd <filename>package</filename>
+git-branch debian
+</programlisting>
+ <para>
+ This puts the orig.tar.gz onto the <emphasis>upstream</emphasis> branch and
+ the Debian patch onto branch <emphasis>debian</emphasis>. Now you can
+ easily modify the package on the master branch, revert changes you made,
+ create other branches for testing, see what changes you made, etc.. When
+ finished just do</para>
+<programlisting>
+git-commit -a
+git-diff debian --
+</programlisting>
+ <para>
+ to get a nice patch that can be submitted to the Debian BTS.
+ </para>
+ </sect1>
</chapter>