applications/gnome-control-center
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
A fork of Gnome-control-center with some tweaks
4017 commits 324 branches 641 tags 195 MiB
C 96.1%
Python 2%
Meson 1.4%
CSS 0.3%
Shell 0.2%
Find a file
Jody Goldberg 8342be7cba check for, but do not require nautilus libs. These is necessary if we move 
2004-05-17  Jody Goldberg <jody@gnome.org>

	* configure.in : check for, but do not require nautilus libs.  These
	  is necessary if we move to the osx/ximian style shell.
2004-05-17 17:03:38 +00:00
archiver Release 2.6.1 2004-04-16 02:32:42 +00:00
capplets For : Michael Terry <mike@mterry.name> 2004-05-17 16:25:01 +00:00
control-center check for, but do not require nautilus libs. These is necessary if we move 2004-05-17 17:03:38 +00:00
debian Initial debian directory 2001-10-24 12:49:00 +00:00
gnome-settings-daemon now the buttons work as Jody asked 2004-05-12 21:54:46 +00:00
help Release 2.6.1 2004-04-16 02:32:42 +00:00
idl Add IDL for SettingsDaemon 2002-03-11 01:44:21 +00:00
libbackground Release 2.6.1 2004-04-16 02:32:42 +00:00
libwindow-settings Release 2.6.1 2004-04-16 02:32:42 +00:00
po check for, but do not require nautilus libs. These is necessary if we move 2004-05-17 17:03:38 +00:00
root-manager fixup localedir to work with solaris gettext (fixes bug #83616) 2002-06-18 19:29:45 +00:00
schemas check for, but do not require nautilus libs. These is necessary if we move 2004-05-17 17:03:38 +00:00
typing-break patch warning 2004-05-11 22:40:34 +00:00
vfs-methods http://bugzilla.gnome.org/show_bug.cgi?id=140342 patched to use argv[0] 2004-05-17 02:49:53 +00:00
.cvsignore No complains on virtual modules 2003-12-01 22:07:07 +00:00
acinclude.m4 http://bugzilla.gnome.org/show_bug.cgi?id=128164 don't use get_real_model. 2004-02-19 05:44:12 +00:00
AUTHORS New and better than ever in a new home 1998-12-08 20:47:55 +00:00
autogen.sh Release 2.6.0.1 2004-03-31 03:35:12 +00:00
ChangeLog check for, but do not require nautilus libs. These is necessary if we move 2004-05-17 17:03:38 +00:00
configure.in check for, but do not require nautilus libs. These is necessary if we move 2004-05-17 17:03:38 +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 merge and update patch from 2004-03-31 21:30:23 +00:00
NEWS check for, but do not require nautilus libs. These is necessary if we move 2004-05-17 17:03:38 +00:00
README remove the png so that it can theme. 2003-12-16 21:38:53 +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

README 

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 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