Handle conflicts between options in different groups. (#156808)

[platform/upstream/glib.git] / README

diff --git a/README b/README
index 66af4c2..40aa60d 100644 (file)
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
 General Information
 ===================
 
-This is GLib version 2.3.2. GLib is the low-level core
+This is GLib version 2.5.4. 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,
@@ -24,26 +24,25 @@ Installation
 
 See the file 'INSTALL'
 
-Notes about GLib-2.2.0
+Notes about GLib-2.4.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
-
-  Also the pseudo-random integers generated by g_rand_int_range and 
-  g_random_int_range will have a slightly better equal distribution
-  with the new version of GLib.
- 
-  The original algorithms, as found in GLib-2.0.x, can be used instead
-  of the new ones by setting the environment variable G_RANDOM_VERSION
-  to the value of "2.0".
-
-  Use the GLib-2.0 algorithms only if you have sequences of numbers
-  generated with Glib-2.0 that you need to reproduce exactly.
+* GObject now enforces CONSTRUCT_ONLY properties; due to an oversight
+  in previous versions, it was possible to set CONSTRUCT_ONLY properties
+  after construct time.
+
+* The child watch functionality tends to reveal a bug in many
+  thread implementations (in particular the older LinuxThreads implementation
+  on Linux) where it's not possible to call waitpid() for a child
+  created in a different thread. For this reason, for maximum portability,
+  you should structure your code to fork all child processes that you want
+  to wait for from the main thread.
+
+* A problem was recently discovered with g_signal_connect_object(); 
+  it doesn't actually disconnect the signal handler once the object being 
+  connected to dies, just disables it. See the API docs for the function 
+  for further details and the correct workaround that will continue to 
+  work with future versions of GLib.
 
 How to report bugs
 ==================