From: Mike Christie <mchristi@redhat.com>
To: target-devel@vger.kernel.org
Subject: Re: tcmu-runner libtcmu.so versioning
Date: Sat, 25 May 2019 23:10:44 +0000 [thread overview]
Message-ID: <5CE9CB74.8070109@redhat.com> (raw)
In-Reply-To: <20190522150417.0650ed2f@suse.de>
On 05/22/2019 08:04 AM, David Disseldorp wrote:
> Hi,
>
> Some ABI changes went into libtcmu between v1.3.0 and v1.4.0 without a
> corresponding .so version bump (e.g. 566c2ad5c8a). This breaks
> dependency checking in some package managers, allowing for a v1.4.0
> tcmu-runner to be installed alongside a v1.3.0 libtcmu.so
>
> Should we consider adding a 2nd (minor) .so version number to libtcmu,
> so that it can be bumped for backwards compatible ABI changes like this
> one?
>
That seems ok to me.
prev parent reply other threads:[~2019-05-25 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 13:04 tcmu-runner libtcmu.so versioning David Disseldorp
2019-05-25 23:10 ` Mike Christie [this message]
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=5CE9CB74.8070109@redhat.com \
--to=mchristi@redhat.com \
--cc=target-devel@vger.kernel.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 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.