From: Jan Engelhardt <jengelh@inai.de>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH] build: bump library versioning
Date: Wed, 16 Sep 2015 19:12:47 +0200 [thread overview]
Message-ID: <1442423567-12120-1-git-send-email-jengelh@inai.de> (raw)
Commit libnftnl-1.0.3-31-g5ea54b2 removed a symbol. Such requires a
bumped to n+1:0:0. The symbol groups can be merged again to save time
processing them as the groups are relative to a particular SONAME
(of which we have a new one).
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
---
This essentially supersedes "[PATCH libnftnl 0/2] map fixes".
The use of LIBNFTNL_4 as a symbol name is modeled upon the LIBVERSION
number. Doing this instead of _x.y is a (more) sensible choice,
because the next modification to the symbol map (LIBNFTNL_5) needs to
be accompanied by LIBVERSION=5:0:something in any case.
src/libnftnl.map | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/src/libnftnl.map b/src/libnftnl.map
index 14ec88c..991fe9d 100644
--- a/src/libnftnl.map
+++ b/src/libnftnl.map
@@ -1,4 +1,4 @@
-LIBNFTNL_1.0 {
+LIBNFTNL_4 {
global:
nft_table_alloc;
nft_table_free;
@@ -397,10 +397,6 @@ global:
nftnl_parse_perror;
-local: *;
-};
-
-LIBNFTNL_1.1 {
nft_table_attr_set_data;
nft_table_attr_get_data;
nft_chain_attr_set_data;
@@ -423,9 +419,6 @@ LIBNFTNL_1.1 {
nftnl_set_set_data;
nftnl_set_get_data;
-} LIBNFTNL_1.0;
-
-LIBNFTNL_1.2 {
nft_set_elems_nlmsg_build_payload_iter;
nft_batch_is_supported;
nft_batch_begin;
@@ -469,9 +462,6 @@ LIBNFTNL_1.2 {
nftnl_gen_fprintf;
-} LIBNFTNL_1.1;
-
-LIBNFTNL_1.2.0 {
nft_ruleset_ctx_is_set;
nft_ruleset_ctx_get;
nft_ruleset_ctx_get_u32;
@@ -506,4 +496,4 @@ LIBNFTNL_1.2.0 {
nftnl_batch_iovec_len;
nftnl_batch_iovec;
-} LIBNFTNL_1.2;
+};
--
2.4.3
next reply other threads:[~2015-09-16 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 17:12 Jan Engelhardt [this message]
2015-09-16 17:28 ` [PATCH] build: bump library versioning Pablo Neira Ayuso
2015-09-16 18:00 ` Pablo Neira Ayuso
2015-09-16 18:22 ` Pablo Neira Ayuso
2015-09-16 18:31 ` Jan Engelhardt
2015-09-16 18:49 ` Pablo Neira Ayuso
2015-09-16 20:40 ` Jan Engelhardt
2015-09-17 11:03 ` Pablo Neira Ayuso
2015-09-16 18:30 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442423567-12120-1-git-send-email-jengelh@inai.de \
--to=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).