All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitrios Siganos <dimitris@siganos.org>
To: buildroot@busybox.net
Subject: [Buildroot] bump libnl to 3.2.21 before release
Date: Sun, 17 Feb 2013 18:49:27 +0000	[thread overview]
Message-ID: <51212637.6020406@siganos.org> (raw)

Hi,

The libnl library versions 3.2.18 and 3.2.19 have an unnecessary
incompatibility problem that has been removed in the later versions.
This problem affected me and went away when I went to 3.2.21.

I suggest we bump the libnl package to 3.2.21, before the release, to
avoid that incompatibility mess.

From libnl website:

Important: 3.2.10 reverted an an uneeded SONAME bump that was done due
to an ABI/API breakage in an unused API. After severe discussion, it was
decided to undo the SONAME bump to make life easier for distribution
maintainers by removing the unused APIs from the public header files and
by providing compat header files that mistakenly included them.

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.

Regards,
Dimitris

             reply	other threads:[~2013-02-17 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 18:49 Dimitrios Siganos [this message]
2013-02-17 18:55 ` [Buildroot] bump libnl to 3.2.21 before release Gustavo Zacarias
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=51212637.6020406@siganos.org \
    --to=dimitris@siganos.org \
    --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.