public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Subslots: should they be bumped like SONAME or on any ABI changes?
Date: Sat, 14 Jun 2014 12:50:56 -0400	[thread overview]
Message-ID: <1402764656.16949.7.camel@rook> (raw)
In-Reply-To: <20140614164151.45afb5ca@pomiot.lan>

[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]

On Sat, 2014-06-14 at 16:41 +0200, Michał Górny wrote:
> Considering the libtool versioning, there are two kinds of library
> bumps relevant to us:
> 
> 1) when ABI is altered in backwards-compatible way (so old stuff is not
> touched),
> 
> 2) when ABI is altered in backwards-incompatible way.

The situation is more nuanced. I have also seen the following cases:

3) a package provides multiple libraries or entry points, and only some
of them have their ABI altered in a backwards-incompatible way.
Examples: xorg-server changes ABI for video drivers, but not for input
drivers; poppler changes ABI for libpoppler, but not libpoppler-glib.

4) a package alters a "private" ABI which matters for a small number of
closely-tied packages, but is transparent to normal users of the
library. Example: glib and gobject-introspection.

A solution to unnecessary rebuilds in these situations, as well as for
case (1), might be in the form of subslots as a key:value list, with
different users subscribing to be rebuilt for specific keys.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-06-14 16:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 14:41 [gentoo-dev] Subslots: should they be bumped like SONAME or on any ABI changes? Michał Górny
2014-06-14 15:13 ` Ciaran McCreesh
2014-06-14 15:32   ` hasufell
2014-06-14 15:45     ` Ciaran McCreesh
2014-06-14 16:04       ` Georg Rudoy
2014-06-14 16:16       ` hasufell
2014-06-14 16:19         ` Ciaran McCreesh
2014-06-14 16:25           ` hasufell
2014-06-14 15:50   ` Alexandre Rostovtsev
2014-06-14 15:56     ` Ciaran McCreesh
2014-06-14 16:17       ` Alexandre Rostovtsev
2014-06-14 16:31         ` Ciaran McCreesh
2014-06-14 16:35           ` Alexandre Rostovtsev
2014-06-14 20:00           ` Rich Freeman
2014-06-14 23:41     ` Patrick Lauer
2014-06-14 16:05 ` Ian Stakenvicius
2014-06-14 16:10   ` [gentoo-dev] " Michael Palimaka
2014-06-14 16:23   ` [gentoo-dev] " hasufell
2014-06-14 16:50 ` Alexandre Rostovtsev [this message]
2014-06-14 16:57   ` Alexandre Rostovtsev
2014-06-14 17:13   ` [gentoo-dev] " Michael Palimaka
2014-06-16  9:47   ` [gentoo-dev] " Pacho Ramos
2014-06-16 10:54     ` Rich Freeman
2014-06-15 19:13 ` Matt Turner
2014-06-16  9:44 ` Pacho Ramos

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=1402764656.16949.7.camel@rook \
    --to=tetromino@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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