X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=HACKING;h=8b6c207b81e7ea24af5c85797d65cdf9c486196e;hb=5b9c687595a464c010024a383e5c140b59fd6774;hp=53ccc8f72c78826d43e1862843f0937d3eb061be;hpb=07e7719441f5927bc3c482717fc53f8529186e3a;p=~andy%2Fgtk

diff --git a/HACKING b/HACKING
index 53ccc8f72..8b6c207b8 100644
--- a/HACKING
+++ b/HACKING
@@ -1,55 +1,64 @@
 If you want to hack on the GTK+ project, you'll need to have
 the following packages installed:
 
-	- 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
+        - GNU autoconf 2.62
+        - GNU automake 1.11
+        - GNU libtool 2.2
+        - indent (GNU indent 1.9.1 is known good)
+        - GNU gettext 10.40
 
 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.
 
-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+.
+Up-to-date instructions about developing GNOME applications and libraries
+can be found here:
 
-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:
+        http://library.gnome.org/devel/
 
-        cvsroot/gtk+# ./autogen.sh
-   
-Basically this does the following for you:
+Information about using git with GNOME can be found here:
 
-  	cvsroot/gtk+# aclocal; automake; autoconf
+        http://live.gnome.org/Git
 
-        The above commands create the "configure" script.  Now you
-	can run the configure script in cvsroot/gtk+ to create all
-	the Makefiles.
+In order to get GIT GTK+ installed on your system, you need to have
+the most recent GIT versions 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+.
 
-Before running autogen.sh or configure, make sure you have libtool 
-in your path.  
+If at all possible, please use GIT to get the latest development version of
+gtk+ and glib. You can do the following to get glib and gtk+ from GIT:
 
-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.
+        $ git clone git://git.gnome.org/glib
+        $ git clone git://git.gnome.org/pango
+        $ git clone git://git.gnome.org/atk
+        $ git clone git://git.gnome.org/gtk+
 
-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:
+Note: if you plan to push changes to back to the master repository and
+have a gnome account, you want to use the following instead:
 
-   $ 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+
+        $ git clone ssh://<username>@git.gnome.org/git/gtk+
+
+To compile the GIT 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:
 
-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.
+        gtk+$ ./autogen.sh
 
+Basically this does the following for you:
+
+        gtk+$ aclocal; automake; autoconf
+
+The above commands create the `configure' script.  Now you
+run the `configure' script in `gtk+/' to create all Makefiles.
+More information about that in `INSTALL'.
+
+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'.
 
+For information about submitting patches and pushing changes
+to GIT, see the `README' and `README.commits' files. In particular,
+don't, under any circumstances, push anything to GIT before
+reading and understanding `README.commmits'.