aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGuido Guenther <agx@sigxcpu.org>2008-03-06 08:52:07 +0100
committerGuido Guenther <agx@sigxcpu.org>2008-03-06 08:52:07 +0100
commit0e08cf54d923db028eff69f4c2a4d99a1f52d774 (patch)
tree70ec35b2718d6e298d33fb202d6bee71d1de2c48
parent647ff4c0af603844a03c1e8025dc1e02371414cd (diff)
explain howto push tags and mention linda and lintian (Closes: #469436)
-rw-r--r--docs/chapters/building.sgml29
1 files changed, 25 insertions, 4 deletions
diff --git a/docs/chapters/building.sgml b/docs/chapters/building.sgml
index 16360b6..02ed91b 100644
--- a/docs/chapters/building.sgml
+++ b/docs/chapters/building.sgml
@@ -2,9 +2,14 @@
<title>Building packages from the &git; repository</title>
<para>
In order to build a &debian; package from the &git; repository you use:
- &git-buildpackage;. During the development phase (when you're either not
- on the <emphasis>debian-branch</emphasis> or when you have uncommitted
- changes in your repository) you'll usually use:
+ &git-buildpackage;. This builds the upstream tarball as will be described below and
+ invokes &debuild; to build the package. To use another build command you
+ can use the <option>--git-builder</option> option as described later in the manual
+ but &debuild; is nice since it can invoke <productname>linda</productname>
+ und <productname>lintian</productname>.
+ During the development phase (when you're either not on the
+ <emphasis>debian-branch</emphasis> or when you have uncommitted changes in
+ your repository) you'll usually use:
<screen>
&git-buildpackage; <option>--git-ignore-new</option>
</screen>
@@ -45,7 +50,6 @@
</screen>
<para>If you want to default to build in a separate build area you can
specify the directory to use in the gbp.conf.
- </para>
<programlisting>
[git-buildpackage]
# use a build area relative to the git repository
@@ -53,5 +57,22 @@ export-dir=../build-area
# to use the same build area for all packages use an absolute path:
#export-dir=/home/debian-packages/build-area
</programlisting>
+ </para>
+ </sect1>
+ <sect1 id="gbp.building.push">
+ <title>Pushing into a remote repository:</title>
+ <para>If you want to push your changes automatically after a succesful build and tag
+ you can use &git-buildpackage;'s posttag hook:
+<programlisting>
+<command>git-buildpackage</command> <option>--git-tag</option> <option>--git-posttag</option>=<replaceable>"git push && git push --tags"</replaceable>
+</programlisting>
+ This assumes you have set up a remote repository to push to in either
+ <filename>.git/config</filename> or
+ <filename>.git/remotes/</filename>. Setting up the posttag hook in
+ <filename>.gbp.conf</filename> looks like:
+<programlisting>
+<option>posttag</option>=<replaceable>"git push git.debian.org && git push --tags git.debian.org"</replaceable>
+</programlisting>
+ </para>
</sect1>
</chapter>