4 This is GLib version 2.1.3. GLib is the low-level core
5 library that forms the basis for projects such as GTK+ and GNOME. It
6 provides data structure handling for C, portability wrappers, and
7 interfaces for such runtime functionality as an event loop, threads,
8 dynamic loading, and an object system.
10 The official ftp site is:
11 ftp://ftp.gtk.org/pub/gtk
13 The official web site is:
16 Information about mailing lists can be found at
17 http://www.gtk.org/mailinglists.html
19 To subscribe: mail -s subscribe gtk-list-request@gnome.org < /dev/null
20 (Send mail to gtk-list-request@gnome.org with the subject "subscribe")
25 See the file 'INSTALL'
27 Notes about GLib-2.2.0
28 ======================
30 * GLib changed the seeding algorithm for the pseudo-random number
31 generator Mersenne Twister, as used by GRand and GRandom. This was
32 necessary, because some seeds would yield very bad pseudo-random
33 streams. Further information can be found at:
35 http://www.math.keio.ac.jp/~matumoto/emt.html
37 The original seeding algorithm, as found in GLib-2.0.x, can be used
38 instead of the new one by setting the environment variable
39 G_RANDOM_VERSION to the value of "2.0". Use the GLib-2.0 algorithm
40 only if you have sequences of numbers generated with Glib-2.0 that
41 you need to reproduce exactly.
46 Bugs should be reported to the GNOME bug tracking system.
47 (http://bugzilla.gnome.org, product glib.) You will need
48 to create an account for yourself.
50 In the bug report please include:
52 * Information about your system. For instance:
54 - What operating system and version
55 - For Linux, what version of the C library
57 And anything else you think is relevant.
59 * How to reproduce the bug.
61 If you can reproduce it with the testgtk program that is built
62 in the gtk/ subdirectory, that will be most convenient. Otherwise,
63 please include a short test program that exhibits the behavior.
64 As a last resort, you can also provide a pointer to a larger piece
65 of software that can be downloaded.
67 * If the bug was a crash, the exact text that was printed out
68 when the crash occured.
70 * Further information such as stack traces may be useful, but
76 Patches should also be submitted to bugzilla.gnome.org. If the
77 patch fixes an existing bug, add the patch as an attachment
80 Otherwise, enter a new bug report that describes the patch,
81 and attach the patch to that bug report.
83 Bug reports containing patches should include the PATCH keyword
84 in their keyword fields. If the patch adds to or changes the GLib
85 programming interface, the API keyword should also be included.
87 Patches should be in unified diff form. (The -u option to GNU