* tcmu-runner libtcmu.so versioning
@ 2019-05-22 13:04 David Disseldorp
2019-05-25 23:10 ` Mike Christie
0 siblings, 1 reply; 2+ messages in thread
From: David Disseldorp @ 2019-05-22 13:04 UTC (permalink / raw)
To: target-devel
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?
Cheers, David
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: tcmu-runner libtcmu.so versioning
2019-05-22 13:04 tcmu-runner libtcmu.so versioning David Disseldorp
@ 2019-05-25 23:10 ` Mike Christie
0 siblings, 0 replies; 2+ messages in thread
From: Mike Christie @ 2019-05-25 23:10 UTC (permalink / raw)
To: target-devel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-05-25 23:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-05-22 13:04 tcmu-runner libtcmu.so versioning David Disseldorp
2019-05-25 23:10 ` Mike Christie
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.