The UUID_1.0 symbol version gratuitously breaks backwards
compatibility in terms of linking with older versions of libuuid.so.1
for no good reason.
Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx>
---
This should be urgently pushed out and a minor released pushed out ASAP,
if you please; thanks!!
- Ted
shlibs/uuid/src/uuid.sym | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/shlibs/uuid/src/uuid.sym b/shlibs/uuid/src/uuid.sym
index 05d9f39..61278f9 100644
--- a/shlibs/uuid/src/uuid.sym
+++ b/shlibs/uuid/src/uuid.sym
@@ -1,12 +1,10 @@
/*
- * The symbol versioning ensures that a new application requiring symbol foo()
- * can't run with old libblkid.so not providing foo() - the global SONAME
- * version info can't enforce this since we never change the SONAME.
- *
- * The original libuuid from e2fsprogs (<=1.41.5) does not to use
- * symbol versioning -- all the original symbols are in UUID_1.0 now.
+ * We should introduce symbol versioning only if we make a backwards
+ * incompatible change or if we make a change to the exported data structures
+ * of which libuuid has very few!
*/
-UUID_1.0 {
+
+{
global:
uuid_clear;
uuid_compare;
@@ -15,7 +13,9 @@ global:
uuid_generate_random;
uuid_generate_time;
uuid_is_null;
+ uuid_pack;
uuid_parse;
+ uuid_unpack;
uuid_unparse;
uuid_unparse_lower;
uuid_unparse_upper;
--
1.6.3.2.1.gb9f7d.dirty
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
