mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2024-09-20 01:06:15 +02:00
c3d01e7332
Sun Oct 25 01:24:01 CST 1998 Shawn T. Amundson <amundson@gtk.org>
* Released GLib 1.1.4
* docs/Makefile.am:
* docs/.cvsignore
* docs/glib-config.1:
* docs/glib.texi: Moved docs from gtk and created glib-config.1
from gtk-config.1 in gtk
* configure.in:
* Makefile.am:
* sanity_check: added in docs directory, change rule 'release'
to 'snapshot' and created a new 'release' rule for doing the
distribution. Added in a 'sanity' rule.
* NEWS:
* README:
* INSTALL: Updated for the release
70 lines
1.8 KiB
Plaintext
70 lines
1.8 KiB
Plaintext
General Information
|
|
===================
|
|
|
|
This is GLib version 1.1.4. GLib, is a library which includes support
|
|
routines for C such as lists, trees, hashes, memory allocation, and
|
|
many other things.
|
|
|
|
Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior
|
|
to 1.1.0.
|
|
|
|
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".
|