4 This is GTK+ version 2.0.0. GTK+ is a multi-platform toolkit
5 for creating graphical user interfaces. Offering a complete set of
6 widgets, GTK+ is suitable for projects ranging from small one-off
7 projects to complete application suites.
9 GTK+ is free software and part of the GNU Project. However, the
10 licensing terms for GTK+, the GNU LGPL, allow it to be used by all
11 developers, including those developing proprietary software, without
12 any license fees or royalties.
14 The official ftp site is:
15 ftp://ftp.gtk.org/pub/gtk
17 The official web site is:
20 Information about mailing lists can be found at
21 http://www.gtk.org/mailinglists.html
26 See the file 'INSTALL'
31 Bugs should be reported to the GNOME bug tracking system.
32 (http://bugzilla.gnome.org, product gtk+.) You will need
33 to create an account for yourself.
35 In the bug report please include:
37 * Information about your system. For instance:
39 - What operating system and version
41 - For Linux, what version of the C library
43 And anything else you think is relevant.
45 * How to reproduce the bug.
47 If you can reproduce it with the testgtk program that is built
48 in the gtk/ subdirectory, that will be most convenient. Otherwise,
49 please include a short test program that exhibits the behavior.
50 As a last resort, you can also provide a pointer to a larger piece
51 of software that can be downloaded.
53 * If the bug was a crash, the exact text that was printed out
54 when the crash occured.
56 * Further information such as stack traces may be useful, but
57 is not necessary. If you do send a stack trace, and the error
58 is an X error, it will be more useful if the stacktrace
59 is produced running the test program with the --sync command
65 Patches should also be submitted to bugzilla.gnome.org. If the
66 patch fixes an existing bug, add the patch as an attachment
69 Otherwise, enter a new bug report that describes the patch,
70 and attach the patch to that bug report.
72 Bug reports containing patches should include the PATCH keyword
73 in their keyword fields. If the patch adds to or changes the GTK
74 programming interface, the API keyword should also be included.
76 Patches should be in unified diff form. (The -u option to GNU