Apply a cleanup patch by Kjartan Maraas (#341812)

[~andy/gtk] / HACKING

diff --git a/HACKING b/HACKING
index ab52d90a99175335338c33126bd6ea1d8841603b..53ccc8f72c78826d43e1862843f0937d3eb061be 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,27 +1,55 @@
-If you want to hack on the Gtk+ project, it will make you life easier
-to have the following packages installed:
+If you want to hack on the GTK+ project, you'll need to have
+the following packages installed:
 
-       - GNU autoconf 2.12
-       - GNU automake 1.2d
-               Available in ftp://ftp.cygnus.com/pub/tromey
-       - GNU libtool 1.0h
-               Available in ftp://alpha.gnu.org/gnu/
+       - GNU autoconf 2.52
+       - GNU automake 1.4
+       - GNU libtool 1.4
+       - indent (GNU indent 1.9.1 is known good)
+       - GNU gettext 10.40
 
-These should be available by ftp from prep.ai.mit.edu or any of the
+These should be available by ftp from ftp.gnu.org or any of the
 fine GNU mirrors.  Beta software can be found at alpha.gnu.org.
 
-If you are accessing gtk+ via CVS, then you will need to take several
-steps to get it to compile.  These are:
+In order to get CVS gtk+ installed on your system, you need to have
+the most recent CVS version of glib, pango, and atk installed as well.
+The installation process of these libraries is similar to that of gtk+, but
+needs to be fulfilled prior to installation of gtk+.
 
-       cvsroot/gtk+# aclocal; automake; autoconf
+To compile a CVS version of gtk+ on your system, you will need to take
+several steps to setup the tree for compilation.  You can do all these
+steps at once by running:
 
-The "configure" script will not exist until you take these steps.
+        cvsroot/gtk+# ./autogen.sh
+   
+Basically this does the following for you:
 
-Before running configure, make sure you have libtool in your path
+       cvsroot/gtk+# aclocal; automake; autoconf
+
+        The above commands create the "configure" script.  Now you
+       can run the configure script in cvsroot/gtk+ to create all
+       the Makefiles.
+
+Before running autogen.sh or configure, make sure you have libtool 
+in your path.  
+
+Note that autogen.sh runs configure for you.  If you wish to pass
+options like --prefix=/usr to configure you can give those options
+to autogen.sh and they will be passed on to configure.
+
+If at all possible, please use CVS to get the latest development version of
+gtk+ and glib.  You can do the following to get glib and gtk+ from cvs:
+
+   $ export CVSROOT=':pserver:anonymous@cvs.gnome.org:/cvs/gnome'
+   $ cvs login
+     (there is no password, just hit return)
+   $ cvs -z3 checkout glib
+   $ cvs -z3 checkout pango
+   $ cvs -z3 checkout atk
+   $ cvs -z3 checkout gtk+
+
+For information about submitting patches and committing changes
+to CVS, see the README and README.cvs-commits files. In particular, 
+don't, under any circumstances, commit anything to CVS before
+reading and understanding README.cvs-commmits.
 
-Please submit patches to the gtk-list@redhat.com mailing list (you must
-subscribe before you post, e-mail gtk-list-request@redhat.com with a
-subject of "subscribe"). All kinds of contributions are accepted. If at
-all possible, please use CVS to get the latest development version of
-gtk+; the README file has the CVSROOT information.