summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJavier Jardón <jjardon@gnome.org>2011-06-06 12:27:17 +0100
committerJavier Jardón <jjardon@gnome.org>2011-06-06 12:27:17 +0100
commit007b7186880bfcdb24498e63f486283d0657fab0 (patch)
tree28b6d193df0b5d6ed0f8c973d1543f0bb87b3b67 /docs
parent7b0d77def54fa0e95fd9a82a2cd2c90e89ecdcd1 (diff)
downloadgtk+-007b7186880bfcdb24498e63f486283d0657fab0.tar.gz
docs: building: gz is not used anymore, but xz instead
Diffstat (limited to 'docs')
-rw-r--r--docs/reference/gtk/building.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/reference/gtk/building.sgml b/docs/reference/gtk/building.sgml
index 9e60e927be..a2fe9a080b 100644
--- a/docs/reference/gtk/building.sgml
+++ b/docs/reference/gtk/building.sgml
@@ -49,12 +49,12 @@ How to compile GTK+ itself
of the tools are already included in the source packages. But
it's useful to know a bit about how packages that use these
tools work. A source package is distributed as a
- <literal>tar.gz</literal> or <literal>tar.bz2</literal> file
+ <literal>tar.bz2</literal> or <literal>tar.xz</literal> file
which you unpack into a directory full of the source files as follows:
</para>
<programlisting>
- tar xvfz gtk+-3.0.0.tar.gz
- tar xvfj gtk+-3.0.0.tar.bz2
+ tar xvfj gtk+-3.2.0.tar.bz2
+ tar xvfJ gtk+-3.2.0.tar.xz
</programlisting>
<para>
In the toplevel directory that is created, there will be