| Revision 20938,
1.7 KB
checked in by ghudson, 20 years ago
(diff) |
|
This commit was generated by cvs2svn to compensate for changes in r20937,
which included commits to RCS files with non-trunk default branches.
|
| Line | |
|---|
| 1 | GNOME Control Center |
|---|
| 2 | ==================== |
|---|
| 3 | |
|---|
| 4 | Requirements - |
|---|
| 5 | |
|---|
| 6 | intltool >= 0.21 |
|---|
| 7 | gtk+ >= 2.3.0 |
|---|
| 8 | gconf >= 2.0.0 |
|---|
| 9 | libgnome >= 2.0.0 |
|---|
| 10 | libgnomeui >= 2.0.0 |
|---|
| 11 | libglade >= 2.0.0 |
|---|
| 12 | libbonobo >= 2.0.0 |
|---|
| 13 | libbonoboui >= 2.0.0 |
|---|
| 14 | libgnomevfs >= 2.0.0 |
|---|
| 15 | gnome-desktop >= 2.0.0 |
|---|
| 16 | gnome-icon-theme >= 1.1.3 |
|---|
| 17 | |
|---|
| 18 | Installation - |
|---|
| 19 | |
|---|
| 20 | See the file 'INSTALL' |
|---|
| 21 | |
|---|
| 22 | How to report bugs - |
|---|
| 23 | |
|---|
| 24 | Bugs should be reported to the GNOME bug tracking system under the product |
|---|
| 25 | control-center. It is available at http://bugzilla.gnome.org. |
|---|
| 26 | |
|---|
| 27 | In the report please include the following information - |
|---|
| 28 | |
|---|
| 29 | Operating system and version |
|---|
| 30 | For Linux, version of the C library |
|---|
| 31 | How to reproduce the bug if possible |
|---|
| 32 | If the bug was a crash, include the exact text that was printed out |
|---|
| 33 | A stacktrace where possible [see below] |
|---|
| 34 | |
|---|
| 35 | How to get a stack trace - |
|---|
| 36 | |
|---|
| 37 | If the crash is reproducible, it is possible to get a stack trace and |
|---|
| 38 | attach it to the bug report. The following steps are used to obtain a |
|---|
| 39 | stack trace - |
|---|
| 40 | |
|---|
| 41 | Run the program in gdb [the GNU debugger] or any other debugger |
|---|
| 42 | ie. gdb gnome-calculator |
|---|
| 43 | Start the program |
|---|
| 44 | ie. (gdb) run |
|---|
| 45 | Reproduce the crash and the program will exit to the gdb prompt |
|---|
| 46 | Get the back trace |
|---|
| 47 | ie. (gdb) bt |
|---|
| 48 | |
|---|
| 49 | Once you have the backtrace, copy and paste this either into the |
|---|
| 50 | 'Comments' field or attach a file with it included. |
|---|
| 51 | |
|---|
| 52 | |
|---|
| 53 | Patches - |
|---|
| 54 | |
|---|
| 55 | Patches should be submitted to bugzilla.gnome.org or emailed to one of |
|---|
| 56 | the people listed in the MAINTAINERS file. If using bugzilla, attach |
|---|
| 57 | the patch to a new bug report [or preferably, check to see if there is |
|---|
| 58 | already a bug report that corresponds to your patch]. Bug reports |
|---|
| 59 | containing patches should include the 'PATCH' keyword. |
|---|
| 60 | |
|---|
| 61 | Patches should be created using the unified diff form. |
|---|
| 62 | ie. cvs diff -u file-to-be-patched.c > patch.diff |
|---|
Note: See
TracBrowser
for help on using the repository browser.
