From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] bump libnl to 3.2.21 before release
Date: Sun, 17 Feb 2013 15:55:56 -0300 [thread overview]
Message-ID: <512127BC.9050004@zacarias.com.ar> (raw)
In-Reply-To: <51212637.6020406@siganos.org>
On 02/17/2013 03:49 PM, Dimitrios Siganos wrote:
> If you linked against 3.2.18 or 3.2.19 your binary will not be
> compatible with >= 3.2.20. You will have to relink your binary. We are
> sorry for any inconvenience this may cause.
>
> Note: The API/ABI that is exported as of 3.2.21 is considered 100%
> stable. No more exceptions that cause confusion and breakage. I will no
> longer merge patches that break API/ABI even though the API seems unused
> at this point. Things have been broken too many times.
The keyword here is "binary".
Breaking ABI isn't important in the buildroot context of packages since
you're building from source thus you don't care about ABI.
It's the same boat like when we moved the openssl package from 0.9.8* to
1.0.*
Is there any explicit problem 3.2.18 causes that affects you?
Regards.
next prev parent reply other threads:[~2013-02-17 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 18:49 [Buildroot] bump libnl to 3.2.21 before release Dimitrios Siganos
2013-02-17 18:55 ` Gustavo Zacarias [this message]
2013-02-17 20:57 ` Dimitrios Siganos
2013-02-17 21:06 ` Gustavo Zacarias
2013-02-17 23:06 ` Dimitrios Siganos
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=512127BC.9050004@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.