1998-07-27 07:33:17 +02:00
|
|
|
General Information
|
|
|
|
|
===================
|
|
|
|
|
|
1999-01-28 09:13:30 +01:00
|
|
|
This is GLib version 1.1.14. GLib, is a library which includes support
|
1998-07-27 07:33:17 +02:00
|
|
|
routines for C such as lists, trees, hashes, memory allocation, and
|
|
|
|
|
many other things.
|
|
|
|
|
|
version bump to 1.1.1, binary age 1, interface age 0. updates. updates.
Tue Aug 4 15:17:54 1998 Tim Janik <timj@gtk.org>
* configure.in: version bump to 1.1.1, binary age 1, interface age 0.
* NEWS: updates.
* README: updates.
* INSTALL: updates and fixes.
* COPYING: include the GNU LGPL, rather than shipping an empty file.
* AUTHORS: listed original authors here, and added people who made
significant improvements to glib.
* glib.h:
* gutils.c: implement g_get_current_dir() which returns a newly
allocated string, instead of a g_getcwd() variant that operates
on a static buffer.
export glib_interface_age and glib_binary_age.
as a convenience, macro definitions have been added for
g_node_insert_data, g_node_insert_data_before, g_node_append_data and
g_node_prepend_data.
* testglib.c: minor cleanups, print current dir.
1998-08-04 16:26:27 +02:00
|
|
|
Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior
|
|
|
|
|
to 1.1.0.
|
1998-07-27 07:33:17 +02:00
|
|
|
|
|
|
|
|
The official ftp site is:
|
|
|
|
|
ftp://ftp.gtk.org/pub/gtk
|
|
|
|
|
|
|
|
|
|
The official web site is:
|
|
|
|
|
http://www.gtk.org/
|
|
|
|
|
|
|
|
|
|
A mailing list is located at:
|
|
|
|
|
gtk-list@redhat.com
|
|
|
|
|
|
|
|
|
|
To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null
|
|
|
|
|
(Send mail to gtk-list-request@redhat.com with the subject "subscribe")
|
|
|
|
|
|
|
|
|
|
Installation
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
See the file 'INSTALL'
|
|
|
|
|
|
|
|
|
|
How to report bugs
|
|
|
|
|
==================
|
|
|
|
|
|
|
|
|
|
To report a bug, send mail either to gtk-list, as mentioned
|
|
|
|
|
above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you
|
|
|
|
|
must be subscribed yourself.
|
|
|
|
|
|
|
|
|
|
In the mail include:
|
|
|
|
|
|
|
|
|
|
* The version of GLib
|
|
|
|
|
|
|
|
|
|
* 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 testglib program that is built
|
|
|
|
|
in the glib/ directory, 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.
|
|
|
|
|
|
|
|
|
|
Patches
|
|
|
|
|
=======
|
|
|
|
|
|
|
|
|
|
Patches can be uploaded to the incoming/ directory on
|
|
|
|
|
ftp.gtk.org. Please follow the instructions there, and include
|
|
|
|
|
your name and email address in the README file.
|
|
|
|
|
|
|
|
|
|
If the patch fixes a bug, it is usually a good idea to include
|
|
|
|
|
all the information described in "How to Report Bugs".
|
