X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=HACKING;h=54c2baea8bcd9655aeead7a1d3b9d2b8658e7460;hb=0dd7155f79407630755764b91bf1baaf7cdf5806;hp=4a3ea44d36c5d8b4b8f4c95962a00dfabac6d1e2;hpb=a33934f5d7559e3077748889417deb891e68a940;p=~andy%2Fgtk diff --git a/HACKING b/HACKING index 4a3ea44d3..54c2baea8 100644 --- a/HACKING +++ b/HACKING @@ -15,45 +15,45 @@ can be found here: http://developer.gnome.org -including information about using Subversion with GNOME: +Information about using git with GNOME can be found here: - http://developer.gnome.org/tools/svn.html + http://live.gnome.org/GitMigration -In order to get SVN gtk+ installed on your system, you need to have -the most recent SVN versions of glib, pango, and atk installed as well. +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+. -If at all possible, please use SVN to get the latest development version of -gtk+ and glib. You can do the following to get glib and gtk+ from SVN: +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: - $ svn checkout http://svn.gnome.org/svn/glib/trunk glib - $ svn checkout http://svn.gnome.org/svn/pango/trunk pango - $ svn checkout http://svn.gnome.org/svn/atk/trunk atk - $ svn checkout http://svn.gnome.org/svn/gtk+/trunk gtk+ + $ 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+ -To compile the SVN version of gtk+ on your system, you will need to take +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: 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. +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 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 committing changes -to SVN, see the `README' and `README.commits' files. In particular, -don't, under any circumstances, commit anything to SVN before +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'.