C Objective-C Python C++ Perl Shell
Fetching latest commit…
Cannot retrieve the latest commit at this time.
General Information =================== This is GLib version 2.1.3. GLib is the low-level core library that forms the basis for projects such as GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system. 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 To subscribe: mail -s subscribe email@example.com < /dev/null (Send mail to firstname.lastname@example.org with the subject "subscribe") Installation ============ See the file 'INSTALL' Notes about GLib-2.2.0 ====================== * GLib changed the seeding algorithm for the pseudo-random number generator Mersenne Twister, as used by GRand and GRandom. This was necessary, because some seeds would yield very bad pseudo-random streams. Further information can be found at: http://www.math.keio.ac.jp/~matumoto/emt.html The original seeding algorithm, as found in GLib-2.0.x, can be used instead of the new one by setting the environment variable G_RANDOM_VERSION to the value of "2.0". Use the GLib-2.0 algorithm only if you have sequences of numbers generated with Glib-2.0 that you need to reproduce exactly. How to report bugs ================== Bugs should be reported to the GNOME bug tracking system. (http://bugzilla.gnome.org, product glib.) 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 - 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. 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 GLib programming interface, the API keyword should also be included. Patches should be in unified diff form. (The -u option to GNU diff.)