tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re:, etc. version numbers? (working on wip/cblas and wip/lapacke)

Am Mon, 11 Jun 2018 11:44:17 -0500
schrieb Jason Bacon <>:

> Shouldn't be too hard to determine the impact of an soversion change.  
> Since they all just include the bl3 file, should be a pretty easy fix 
> too.  The .4 symlink would probably do it, if it's even necessary.

We can trigger all dependent packages to be re-built, right? Are there
examples I can look at for the specifics? If it is acceptable to have
them broken for a while until things are rebuilt, we can settle on
that. If we even can trigger the .so.4 symlink being deleted after the
rebuilds, it could be a clean affair with minimal breakage. Downside is
that this has limited testing.

How much of a no-go is an upgrade that replaces the .so.4 with an so.3
and just tells users to rebuild things? Increment the revision of the
dependent packages as trigger to rebuild on update?

Alrighty then,


Dr. Thomas Orgis
Universität Hamburg
RRZ / Basis-Infrastruktur / HPC
Schlüterstr. 70
20146 Hamburg
Tel.: 040/42838 8826
Fax: 040/428 38 6270

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Home | Main Index | Thread Index | Old Index