diff options
author | Elijah Newren <newren gmail com> | 2007-09-01 18:50:07 +0000 |
---|---|---|
committer | Elijah Newren <newren@src.gnome.org> | 2007-09-01 18:50:07 +0000 |
commit | eb3c38e3adb8034513e8cf43202f5da39a6964be (patch) | |
tree | f71a17e29785676c00205420b5bb314c36b5d8f4 /HACKING | |
parent | 5196fb1ec505445808aa657108ed3f97482208ea (diff) | |
download | metacity-eb3c38e3adb8034513e8cf43202f5da39a6964be.tar.gz |
update; cvs->svn & mention GConf needed Make it match idiotic format
2007-09-01 Elijah Newren <newren gmail com>
* HACKING: update; cvs->svn & mention GConf needed
* MAINTAINERS: Make it match idiotic format requirements (I love
you Olav!)
svn path=/trunk/; revision=3317
Diffstat (limited to 'HACKING')
-rw-r--r-- | HACKING | 23 |
1 files changed, 11 insertions, 12 deletions
@@ -42,18 +42,17 @@ Minimal Building/Testing Environment build a development version of Metacity -- odds are, you may be able to build metacity from CVS without building any other modules. - As long as you have gtk+ >= 2.10 with your distro (gtk+ >= 2.6 if - you manually revert the change from bug 348633), you should be able - to install your distro's development packages (e.g. gtk2-devel, - GConf2-devel, startup-notification-devel on Fedora; also, remember - to install the gnome-common package which is needed for building cvs - versions of Gnome modules like Metacity) as well as the standard - development tools (gcc, autoconf, automake, pkg-config, intltool, - and libtool) and be ready to build and test Metacity. Steps to do - so: - - $ cvs -q -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome \ - checkout metacity + As long as you have gtk+ >= 2.10 and GConf with your distro (gtk+ >= + 2.6 if you manually revert the change from bug 348633), you should + be able to install your distro's development packages + (e.g. gtk2-devel, GConf2-devel, startup-notification-devel on + Fedora; also, remember to install the gnome-common package which is + needed for building cvs versions of Gnome modules like Metacity) as + well as the standard development tools (gcc, autoconf, automake, + pkg-config, intltool, and libtool) and be ready to build and test + Metacity. Steps to do so: + + $ svn checkout http://svn.gnome.org/svn/metacity/trunk metacity $ cd metacity $ ./autogen.sh --prefix /usr $ make |