Bug#813128: Fwd: Bug#813128: transition: openmpi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Le 15/02/2016 21:57, Mattia Rizzolo a écrit :
> On Mon, Feb 15, 2016 at 09:31:43PM +0100, Thibaut Paumard wrote:
>> Le 15/02/2016 19:27, Matthias Klose a écrit :
>>> On 15.02.2016 19:21, Mattia Rizzolo wrote:
>>>> On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose
>>>> wrote:
>>>>> For this, /usr/share/mpi-default-dev/debian_defaults would
>>>>> need a new macro openmpi_archs = ...
>>>>
>>>> that's not possible, since the current mpi-defaults structure
>>>> is "use openmpi everywhere, except in those 3 arch where we
>>>> want mpich". the openmpi architectures are not listed in
>>>> mpi-defaults.
>>>
>>> I was suggessting to add such a macro.
>>
>> Indeed it would be helpful to have a openmpi_archs macro
>> available. I think we would also need a mpich_archs macro by
>> symmetry, then one would be really able to generate
>> debian/control so the list of arches each binary packages must be
>> built for is correct automatically at the time you upload the
>> package.
>
> then mpi-defaults would need a sourceful uploads every single time
> a new architecture is added (and we want to support MPI there and
> openmpi builds), and also suddenly file a dozen RC bugs (as all
> packages using such a system would start to fail). Yes, we can do
> it, though.
So, what we want if to render RC buggy some packages that need a
source upload whenever OPENMPI_ARCHITECTURES or MPICH_ARCHITECTURES
change.
An easier way would be for those packages to have a versioned
dependency on mpi-default-dev and bump this version when either
variable changes, e.g.
Build-Depends: mpi-default-dev (>= 1.3), mpi-default-dev (<< 1.4~)
This is assuming the minor part of the version of mpi-default-dev
changes when either variable changes. The version can then have also a
micro digit, to allow for new versions that don't change these variables
.
Actually a versioned dependency seems required anyway since you know
your new package will FTBFS with earlier versions of mpi-default-dev.
The only thing is that you can also predict that later versions of
mpi-default-dev will break your package.
This discussion getting off-topic for this bug, should we move
somewhere else?
Regards, Thibaut.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWwvvfAAoJEJOUU0jg3ChAJXQP/At/3l6QCBDH+FTcqqglksiT
l45CXlAsV1JT+JIZ2+oCoFHgHbOmtwwg0KBM7o9Mz5MOVN2te3YIPwioFANgE79S
gEYx7HQA0ushOl3kgil1mwtVeh4YLRuYR7NZt2Bt5UEzKkSsH/UUU0PQEI3xrTqR
ADL0miop0TgBYjM5/hYRlbitAFxYM0vRUoj46G/pOTnP7JCvOkswaDuEkPIGyc/8
bW4/sUvG3mQO++hGm6IBRRiuusgEESaAgKdDAZzjRxZP8x8zc5e+OcXUdDUIlaVx
9PWE4xRwJwk/i/L9waV5UL3B3JYPt/5K5u2OrPez2fMe61bsntZDY4/odv38YI8n
oZopJ+WpP295pEs3D1TFCNy3HNQIUebER5V2daqIgoocGbZ+8ShEwvBP2u3BYTLG
PX0i7vOsTXeWckFfTorH5Sa0awPmIyTAPO296kxPR4CHuWPwfftVDbJz/0gAaWfd
HKc8CdL23Gsp8Cg7pQodicwSYbDbO8LsbEiWQaW+KSwj2d/EVGSckAGUXFcWj/fZ
7URVEjo+6jDXryd5yFo2nCgA+A/EbQQKm5MRn/f8IJ4MuOMhJy/GT7Oz+J6bm11+
aMx8X1eMna+u3M2zChgQJh+Q5p99WDUAkQqmnbJ9/SxXhrm51GMGhwzAbrUVDb5m
UfoWW/ggFQGWv0E8yRma
=dnON
-----END PGP SIGNATURE-----
Reply to: