Bug#953021: libhdf5-mpi-dev: provide links to default mpi (hdf5-mpi.pc)

Gilles Filippini pini at debian.org
Tue Mar 17 16:59:58 GMT 2020


Gilles Filippini a écrit le 16/03/2020 à 17:56 :
> Hi Drew,
> 
> Drew Parsons a écrit le 03/03/2020 à 19:43 :
>> Thinking about it, if possible it would be best to have hdf5-mpi.pc
>> managed by update-alternatives, but tracking the mpi alternative.
>>
>> i.e. set up as a slave alternative depending on mpi, that updates if the
>> local system switches mpi from openmpi to mpich.
>>
>> I'm not sure if this can be done cross-package, but good if it can.
>>
>> If it can be done, then the control logic would go in the postinst/prerm
>> of libhdf5-openmpi-dev and libhdf5-mpich-dev rather than libhdf5-mpi-dev.
> 
> I'm not sure what you have in mind here. I've just uploaded a new
> release to experimental which should fix #953020. It may covers #953021
> as well. Please let me know...

As I understand it now, this is do-able if and only if there is a way to
add a slave to an existing alternative. But I can't find such a way. Any
idea?

Thanks,

_g.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-grass-devel/attachments/20200317/63360437/attachment.sig>


More information about the Pkg-grass-devel mailing list