Removed empty docs/reference/ChangeLog entries. I am using prepare-ChangeLog.pl to...

[~andy/gtk] / HACKING

diff --git a/HACKING b/HACKING
index 642e4c35ce21f14956a436939e54caeac7a44bdb..91dd2156ea0479528492e1bf590e7839dc5cb0b5 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -1,54 +1,64 @@
-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.3
-               (Beta releases are at ftp://ftp.cygnus.com/pub/tromey)
-       - GNU libtool 1.2b
-       - indent (GNU indent 1.9.1 is known good)
+        - GNU autoconf 2.54
+        - GNU automake 1.7
+        - GNU libtool 1.4
+        - 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.
 
 
 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 installed as well.
-The installation process of glib is similar to that of gtk+, but
+Up-to-date instructions about developing GNOME applications and libraries
+can be found here:
+
+        http://developer.gnome.org
+
+Information about using git with GNOME can be found here:
+
+        http://live.gnome.org/Git
+
+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+.
 
 needs to be fulfilled prior to installation of gtk+.
 

-To compile a CVS version of gtk+ on your system, you will need to take
+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:
+
+        $ 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+
+
+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:
+
+        $ 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:
 
 several steps to setup the tree for compilation.  You can do all these
 steps at once by running:
 

-        cvsroot/gtk+# ./autogen.sh
-   
+        gtk+$ ./autogen.sh
+

 Basically this does the following for you:
 
 Basically this does the following for you:
 

-       cvsroot/gtk+# aclocal; automake; autoconf
+        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.
+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.  
+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
 
 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.gimp.org:/debian/home/gnomecvs'
-   $ cvs login
-     (there is no password, just hit return)
-   $ cvs -z9 checkout glib
-   $ cvs -z9 checkout gtk+
-
-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.
-Patches that you wish to go into the distribution should also be uploaded 
-to ftp://ftp.gimp.org/incoming.  Follow the rules there for naming your
-patches. 
+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'.