4 This is GLib version @GLIB_VERSION@. 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.4.0
28 ======================
30 * g_filename_to_uri() used to operate like this:
32 1. convert the filename from G_FILENAME_ENCODING to UTF-8
33 2. encode the UTF-8 into hexadecimal escapes for URIs
35 This was incorrect, and now the filename is simply escaped for
36 conversion into URIs. g_filename_from_uri() is fixed in the same
37 fashion. Programs which store the converted URIs or filenames may
38 need manual conversion.
40 * GObject now enforces CONSTRUCT_ONLY properties; due to an oversight
41 in previous versions, it was possible to set CONSTRUCT_ONLY properties
44 * The child watch functionality tends to reveal a bug in many
45 thread implementations (in particular the older LinuxThreads implementation
46 on Linux) where it's not possible to call waitpid() for a child
47 created in a different thread. For this reason, for maximum portability,
48 you should structure your code to fork all child processes that you want
49 to wait for from the main thread.
51 * A problem was recently discovered with g_signal_connect_object();
52 it doesn't actually disconnect the signal handler once the object being
53 connected to dies, just disables it. See the API docs for the function
54 for further details and the correct workaround that will continue to
55 work with future versions of GLib.
60 Bugs should be reported to the GNOME bug tracking system.
61 (http://bugzilla.gnome.org, product glib.) You will need
62 to create an account for yourself.
64 In the bug report please include:
66 * Information about your system. For instance:
68 - What operating system and version
69 - For Linux, what version of the C library
71 And anything else you think is relevant.
73 * How to reproduce the bug.
75 If you can reproduce it with the testgtk program that is built
76 in the gtk/ subdirectory, that will be most convenient. Otherwise,
77 please include a short test program that exhibits the behavior.
78 As a last resort, you can also provide a pointer to a larger piece
79 of software that can be downloaded.
81 * If the bug was a crash, the exact text that was printed out
82 when the crash occured.
84 * Further information such as stack traces may be useful, but
90 Patches should also be submitted to bugzilla.gnome.org. If the
91 patch fixes an existing bug, add the patch as an attachment
94 Otherwise, enter a new bug report that describes the patch,
95 and attach the patch to that bug report.
97 Bug reports containing patches should include the PATCH keyword
98 in their keyword fields. If the patch adds to or changes the GLib
99 programming interface, the API keyword should also be included.
101 Patches should be in unified diff form. (The -u option to GNU