X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=HACKING;h=e04e0dcdd9c007ca78d9af4f0d7fe97d05ca25cc;hb=2a53b4d0e2c98a14aedf31e38f0ad1fb2e8fe26f;hp=e4001c75fd07bd9a3ef12b57450c650cabd8b478;hpb=c01596714fb7651ddc87576ec7aac19a021ae898;p=platform%2Fupstream%2Fglib.git

diff --git a/HACKING b/HACKING
index e4001c7..e04e0dc 100644
--- a/HACKING
+++ b/HACKING
@@ -1,39 +1,37 @@
-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 GLib project, you'll need to have the
+following packages installed:
 
-	- GNU autoconf 2.13
-	- GNU automake 1.4
-	        (Beta releases are at ftp://ftp.cygnus.com/pub/tromey)
-	- GNU libtool 1.2d
+        - GNU autoconf 2.62
+        - GNU automake 1.11
+        - GNU libtool 2.2
+        - GNU gettext 0.10.40
+        - pkg-config 0.16
+        - gtk-doc
+        - libffi 3.0.0
 
 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.
 
-To compile a CVS version of glib on your system, you will need to take
+To compile a GIT version of glib 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:
 
-        cvsroot/glib# ./autogen.sh
-   
+        checkout/glib# ./autogen.sh
+
 Basically this does the following for you:
 
-  	cvsroot/glib# aclocal; automake; autoconf
+        checkout/glib# aclocal; automake; autoconf
 
         The above commands create the "configure" script.  Now you
-	can run the configure script in cvsroot/glib to create all
-	the Makefiles.
+        can run the configure script in checkout/glib to create all
+        the Makefiles.
 
-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
 options like --prefix=/usr to configure you can give those options
 to autogen.sh and they will be passed on to configure.
 
-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. 
-
+For information about submitting patches see the README.commits file. For
+information about major design decisions, see the README.rationale file.