X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=README.in;h=6a86f85347ebeb45677540c95a98bc9fcdad3a9e;hb=2a53b4d0e2c98a14aedf31e38f0ad1fb2e8fe26f;hp=1122c1674a037bf0ba3e112680f801cbbbaa741b;hpb=6262a48678c2104617a9d329668e878bbbf1fb7f;p=platform%2Fupstream%2Fglib.git

diff --git a/README.in b/README.in
index 1122c16..6a86f85 100644
--- a/README.in
+++ b/README.in
@@ -67,6 +67,24 @@ and attach the patch to that bug report.
 
 Patches should be in unified diff form. (The -up option to GNU diff.)
 
+Notes about GLib 2.40
+=====================
+
+* g_test_run() no longer runs tests in exactly the order they are
+  registered; instead, it groups them according to test suites (ie,
+  path components) like the documentation always claimed it did. In
+  some cases, this can result in a sub-optimal ordering of tests,
+  relative to the old behavior. The fix is to change the test paths to
+  properly group together the tests that should run together. (eg, if
+  you want to run test_foo_simple(), test_bar_simple(), and
+  test_foo_using_bar() in that order, they should have test paths like
+  "/simple/foo", "/simple/bar", "/complex/foo-using-bar", not
+  "/foo/simple", "/bar/simple", "/foo/using-bar" (which would result
+  in test_foo_using_bar() running before test_bar_simple()).
+
+  (The behavior actually changed in GLib 2.36, but it was not
+  documented at the time, since we didn't realize it mattered.)
+
 Notes about GLib 2.36
 =====================
 
@@ -74,6 +92,11 @@ Notes about GLib 2.36
   loading GLib as a dynamic module, you should be careful to avoid
   unloading it, then subsequently loading it again.  This never
   really worked before, but it is now explicitly undefined behavior.
+  Note that if g_type_init() was the only explicit use of a GObject
+  API and you are using linker flags such as --no-add-needed, then
+  you may have to artificially use some GObject call to keep the
+  linker from optimizing away -lgobject. We recommend to use
+  g_type_ensure (G_TYPE_OBJECT) for this purpose.
 
 * This release contains an incompatible change to the g_get_home_dir()
   function.  Previously, this function would effectively ignore the HOME
@@ -81,6 +104,12 @@ Notes about GLib 2.36
   As of this version, the HOME variable is used if it is set and the
   value from /etc/passwd is only used as a fallback.
 
+* The 'flowinfo' and 'scope_id' fields of GInetSocketAddress
+  (introduced in GLib 2.32) have been fixed to be in host byte order
+  rather than network byte order. This is an incompatible change, but
+  the previous behavior was clearly broken, so it seems unlikely that
+  anyone was using it.
+
 Notes about GLib 2.34
 =====================