A fork of Gnome-control-center with some tweaks
Find a file
2003-02-10 09:18:27 +00:00
archiver 2.2.0.1 2003-02-04 23:53:43 +00:00
capplets get the default from the schema and always sort it at the top. 2003-02-05 22:20:09 +00:00
control-center 2.2.0.1 forgot to commit this last night. 2003-02-05 15:45:30 +00:00
debian Initial debian directory 2001-10-24 12:49:00 +00:00
gnome-settings-daemon handle xcursor so that we support Xcursor files. 2003-02-06 21:47:00 +00:00
help 2.2.0.1 forgot to commit this last night. 2003-02-05 15:45:30 +00:00
idl Add IDL for SettingsDaemon 2002-03-11 01:44:21 +00:00
libbackground 2.2.0.1 forgot to commit this last night. 2003-02-05 15:45:30 +00:00
libwindow-settings 2.2.0.1 forgot to commit this last night. 2003-02-05 15:45:30 +00:00
po 2.2.0.1 forgot to commit this last night. 2003-02-05 15:45:30 +00:00
root-manager fixup localedir to work with solaris gettext (fixes bug #83616) 2002-06-18 19:29:45 +00:00
schemas fixed more typos 2002-12-17 16:24:56 +00:00
vfs-methods/fontilus Added Ukrainian translation 2003-02-10 09:18:27 +00:00
.cvsignore add 2002-04-19 19:24:22 +00:00
acinclude.m4 Use gettext 0.10.35 Removed `sed POTFILES...'. Removed gettext macros. 1998-12-02 18:18:48 +00:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh Cleanup for GNOME 2 port Allow disabling of screensaver capplet compile if 2001-10-26 19:11:30 +00:00
ChangeLog 2.2.0.1 2003-02-04 23:53:43 +00:00
configure.in 2.2.0.1 2003-02-04 23:53:43 +00:00
control-center.spec.in Use sysconfdir=/etc 1999-08-19 17:03:02 +00:00
control-center2.png fixed AA of the wrench 2002-01-17 21:04:46 +00:00
COPYING add 2002-04-19 19:24:22 +00:00
MAINTAINERS take the blame 2002-12-11 05:56:42 +00:00
Makefile.am - Jody forgot to remove help from the top-level Makefile.am as well, removed here 2002-05-29 17:36:16 +00:00
NEWS 2.1.7 2003-01-16 07:59:09 +00:00
README http://bugzilla.gnome.org/show_bug.cgi?id=100916 2002-12-30 17:49:43 +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  
====================
Version: 2.1.4

GNOME Control Center for the GNOME 2.2 Beta Desktop contains the following -

	gnome-accessibility-keyboard-properties	
	gnome-background-properties	
	gnome-default-applications-properties
	gnome-file-types-properties
	gnome-font-properties
	gnome-keybinding-properties
	gnome-keyboard-properties
	gnome-mouse-properties
	gnome-network-preferences
	gnome-sound-properties
	gnome-theme-manager
	gnome-ui-properties
	gnome-window-properties
	gnome-control-center
	gnome-settings-daemon 

Requirements -

	intltool	>= 0.21
	gtk+		>= 2.0.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
	
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 one of
the people listed in the MAINTAINERS file. 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 -u file-to-be-patched.c > patch.diff