Enhanced symbol versioning in 2.7.x

[Andreas Metzler]

Hello,

with 2.7.x you seem to have started to use a different symbol
versioning for newly added symbols (since 2.6.x). Well, at least that
is my understanding. ;-) I am not sure abut the point, is this for
RedHats automatically versioned library dependencies?

Anyway, I think this patch should be applied,
gnutls_x509_crq_set_key is already present in 2.6.6, versioning it
@GNUTLS_2_8 would break the ABI, afaik.

--- libgnutls.map.orig  2009-05-20 20:53:15.000000000 +0200
+++ libgnutls.map       2009-05-20 20:54:14.000000000 +0200
@@ -414,6 +414,7 @@
     gnutls_x509_crq_set_basic_constraints;
     gnutls_x509_crq_set_challenge_password;
     gnutls_x509_crq_set_dn_by_oid;
+    gnutls_x509_crq_set_key;
     gnutls_x509_crq_set_key_rsa_raw;
     gnutls_x509_crq_set_key_usage;
     gnutls_x509_crq_set_version;
@@ -564,7 +565,6 @@
     gnutls_x509_crq_get_subject_alt_othername_oid;
     gnutls_x509_crq_get_extension_by_oid;
     gnutls_x509_crq_set_subject_alt_name;
-    gnutls_x509_crq_set_key;
     gnutls_x509_crq_get_key_purpose_oid;
     gnutls_x509_crq_set_key_purpose_oid;
     gnutls_x509_crq_print;

I assume that if there was a soname bump we would change from
--------------
GNUTLS_1_4
{
...
};

GNUTLS_2_8
{
...
} GNUTLS_1_4;

GNUTLS_PRIVATE {
};
--------------

to 

--------------
GNUTLS_2_10
{
[symbols listed previously in GNUTLS_1_4 or GNUTLS_2_8 go here]
};


GNUTLS_PRIVATE_2_10 {
[symbols listed previously in GNUTLS_PRIVATE go here]
};
--------------
Am I correct?

cu andreas

 
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'