A fork of Gnome-control-center with some tweaks
Find a file
Rodrigo Moya 7b6f60b5bb just read the file from the $datadir we installed it.
2006-01-16  Rodrigo Moya <rodrigo@novell.com>

	* gnome-da-xml.c (gnome_da_xml_load_list): just read the file
	from the $datadir we installed it.

	* Makefile.am: -DDATADIR.
2006-01-16 17:59:03 +00:00
archiver Here too 2005-05-11 16:07:51 +00:00
capplets just read the file from the $datadir we installed it. 2006-01-16 17:59:03 +00:00
control-center added method for setting single click policy track for changes in the 2006-01-11 18:33:34 +00:00
debian Initial debian directory 2001-10-24 12:49:00 +00:00
gnome-settings-daemon optional use of gstreamer0.10, patch based on the work 2006-01-15 21:56:50 +00:00
help fix the make distcheck. 2005-07-27 13:35:45 +00:00
idl Add IDL for SettingsDaemon 2002-03-11 01:44:21 +00:00
libbackground Handle the new WPTYPE_ZOOM setting and return proper geometry for it 2006-01-14 13:38:55 +00:00
libwindow-settings Huge cleanup. Individual ChangeLogs have info. Closing bug #320157. ANSIfy 2005-11-14 15:18:09 +00:00
m4 switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
po Updated Canadian English translation. 2006-01-16 04:23:41 +00:00
root-manager fixup localedir to work with solaris gettext (fixes bug #83616) 2002-06-18 19:29:45 +00:00
schemas drop the keysym/keycode binding code, it's an hack and 2006-01-11 15:10:13 +00:00
typing-break Fixes #326141 2006-01-09 12:22:34 +00:00
vfs-methods don't call gnome_theme_init (), it's not required. Speedup of 15-20%. 2005-11-14 15:35:46 +00:00
.cvsignore switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
ChangeLog the new gnome-default-applications capplet uses libxml2 2006-01-16 15:15:28 +00:00
configure.in the new gnome-default-applications capplet uses libxml2 2006-01-16 15:15:28 +00:00
control-center.spec.in require either xscreensaver or gnome-screensaver. 2005-07-25 11:56:28 +00:00
COPYING add 2002-04-19 19:24:22 +00:00
MAINTAINERS Added seb128 to MAINTAINERS 2005-10-24 09:20:34 +00:00
Makefile.am switch to gnome-doc-utils, require 1.9 to build the tarball correctly 2005-07-27 12:56:39 +00:00
NEWS NEWS; update for 2.13.4. 2006-01-03 19:23:03 +00:00
README Added info about gnomecc-list 2005-10-13 22:03:28 +00:00
TODO update TODO list 2002-04-10 02:04:23 +00:00
TODO.xml Fixed typo in TODO.xml file 2000-10-08 19:19:44 +00:00

GNOME Control Center  
====================

Requirements -

	intltool	>= 0.21
	gtk+		>= 2.3.0
	gconf		>= 2.0.0
	libgnome	>= 2.0.0
	libgnomeui	>= 2.0.0
	libglade	>= 2.0.0
	libbonobo	>= 2.0.0
	libbonoboui	>= 2.0.0
	libgnomevfs	>= 2.0.0
	gnome-desktop	>= 2.0.0
	gnome-icon-theme >= 1.1.3
	
Installation -

See the file 'INSTALL'

How to report bugs -

Bugs should be reported to the GNOME bug tracking system under the product
control-center. It is available at http://bugzilla.gnome.org. 

In the report please include the following information -

	Operating system and version
	For Linux, version of the C library
	How to reproduce the bug if possible
	If the bug was a crash, include the exact text that was printed out
	A stacktrace where possible [see below]

How to get a stack trace -

If the crash is reproducible, it is possible to get a stack trace and 
attach it to the bug report. The following steps are used to obtain a 
stack trace -
	
	Run the program in gdb [the GNU debugger] or any other debugger
		ie. gdb gnome-calculator
	Start the program
		ie. (gdb) run
	Reproduce the crash and the program will exit to the gdb prompt
	Get the back trace
		ie. (gdb) bt

Once you have the backtrace, copy and paste this either into the 
'Comments' field or attach a file with it included.


Patches -

Patches should be submitted to bugzilla.gnome.org or emailed to the 
gnomecc-list@gnome.org list. If using bugzilla, attach
the patch to a new bug report [or preferably, check to see if there is
already a bug report that corresponds to your patch]. Bug reports 
containing patches should include the 'PATCH' keyword.

Patches should be created using the unified diff form.
	ie. cvs diff -up file-to-be-patched.c > patch.diff