forked from AuroraMiddleware/gtk
26ac563f16
Thu Mar 7 23:29:35 2002 Owen Taylor <otaylor@redhat.com>
* NEWS: Final updates for 2.0.0
* README.in: Updates.
78 lines
2.3 KiB
Plaintext
78 lines
2.3 KiB
Plaintext
General Information
|
|
===================
|
|
|
|
This is GTK+ version 2.0.0. GTK+ is a multi-platform toolkit
|
|
for creating graphical user interfaces. Offering a complete set of
|
|
widgets, GTK+ is suitable for projects ranging from small one-off
|
|
projects to complete application suites.
|
|
|
|
GTK+ is free software and part of the GNU Project. However, the
|
|
licensing terms for GTK+, the GNU LGPL, allow it to be used by all
|
|
developers, including those developing proprietary software, without
|
|
any license fees or royalties.
|
|
|
|
The official ftp site is:
|
|
ftp://ftp.gtk.org/pub/gtk
|
|
|
|
The official web site is:
|
|
http://www.gtk.org/
|
|
|
|
Information about mailing lists can be found at
|
|
http://www.gtk.org/mailinglists.html
|
|
|
|
Installation
|
|
============
|
|
|
|
See the file 'INSTALL'
|
|
|
|
How to report bugs
|
|
==================
|
|
|
|
Bugs should be reported to the GNOME bug tracking system.
|
|
(http://bugzilla.gnome.org, product gtk+.) You will need
|
|
to create an account for yourself.
|
|
|
|
In the bug report please include:
|
|
|
|
* Information about your system. For instance:
|
|
|
|
- What operating system and version
|
|
- What version of X
|
|
- For Linux, what version of the C library
|
|
|
|
And anything else you think is relevant.
|
|
|
|
* How to reproduce the bug.
|
|
|
|
If you can reproduce it with the testgtk program that is built
|
|
in the gtk/ subdirectory, that will be most convenient. Otherwise,
|
|
please include a short test program that exhibits the behavior.
|
|
As a last resort, you can also provide a pointer to a larger piece
|
|
of software that can be downloaded.
|
|
|
|
* If the bug was a crash, the exact text that was printed out
|
|
when the crash occured.
|
|
|
|
* Further information such as stack traces may be useful, but
|
|
is not necessary. If you do send a stack trace, and the error
|
|
is an X error, it will be more useful if the stacktrace
|
|
is produced running the test program with the --sync command
|
|
line option.
|
|
|
|
Patches
|
|
=======
|
|
|
|
Patches should also be submitted to bugzilla.gnome.org. If the
|
|
patch fixes an existing bug, add the patch as an attachment
|
|
to that bug report.
|
|
|
|
Otherwise, enter a new bug report that describes the patch,
|
|
and attach the patch to that bug report.
|
|
|
|
Bug reports containing patches should include the PATCH keyword
|
|
in their keyword fields. If the patch adds to or changes the GTK
|
|
programming interface, the API keyword should also be included.
|
|
|
|
Patches should be in unified diff form. (The -u option to GNU
|
|
diff.)
|