On 2019-10-18 15:56, Emilio Pozuelo Monfort wrote:
On 17/10/2019 17:05, Drew Parsons wrote:
Hi Emilio, this is rather awkward. Hypre upstream has just released
2.18.1, so
this would be the one to run the transition on.
...
"The hypre team currently does nothing to ensure application binary
interface
(ABI) compatibility. As a result, all releases (major, minor, or
patch) should
be treated as incompatible."
It means we have to run a new library package for each patch release,
and
therefore have to jump back into the NEW queue with libhypre-2.18.1.
It's
either that, or provide only a generic libhypre package and apply
rigidly strict
shlib files depending strictly on a given version.
...
Right, the strict dependency via shlibs and provides would make testing
migrations harder as everything would need to transition at the same
time (hypre
and all rdeps). However there are three rdeps and you control two of
them, so it
doesn't look like a terrible situation.
hypre 2.18.1 is now ready in experimental.
I've implemented the common libhypre option with shlibs patch-version
dependency. If this approach proves problematic in practice then we can
switch back to version-based library package names afterwards if we need
to.
I've confirmed petsc and sundials build successfully.
Let's do this transition.
Drew
