public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Turner <mattst88@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: Sun, 15 Jun 2014 12:13:44 -0700	[thread overview]
Message-ID: <CAEdQ38EkJ1Jgwn1S4GdivY2+nXdxG+JYNAiA-Gz9_6xc_zcBOQ@mail.gmail.com> (raw)
In-Reply-To: <20140614164151.45afb5ca@pomiot.lan>

On Sat, Jun 14, 2014 at 7:41 AM, Michał Górny <mgorny@gentoo.org> wrote:
> Hi,
>
> Some time ago we've got bug #510780 [1] asking us to bump subslot
> on LLVM even though the new version was ABI-compatible with previous
> one. It was because it introduced new APIs which applications could
> make use of. Since I believe this is a wider issue, I would like to
> know the opinion of our community about this.
>
> More specifically: do we want subslots to change only when backwards-
> incompatible ABI changes are done -- alike SONAME -- or whenever any
> ABI change is done? The problem seems a bit complex.

I think subslot should only change with SONAME. Packages depending on
a new API can use a versioned dependency to ensure the new API is
available.

I think this covers all of the cases and doesn't cause problems? Let
me know if I've misunderstood something.


  parent reply	other threads:[~2014-06-15 19:14 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
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 [this message]
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=CAEdQ38EkJ1Jgwn1S4GdivY2+nXdxG+JYNAiA-Gz9_6xc_zcBOQ@mail.gmail.com \
    --to=mattst88@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