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.
> However any change in this list will still require a source upload and I
> fail to see how to detect automatically that such an upload is needed.
there are people costantly rebuilding the archive nowadays
(*tsk*reproducible build folk*tsk*) and they would notice that packages
start failing after such change.
I'm thinking about this postgres thing. Now, that one is way too
complex for this case, probably, but it would be nice.
https://sources.debian.net/src/postgresql-common/unstable/pgxs_debian_control.mk/
Yet, I'm not going to implement such thing, I can't put myself in such
a journey.
I can teach mpi-defaults to provide OPENMPI_ARCHITECTURES and
MPICH_ARCHITECTURES, and also making that debian/control more format
about them (e.g., it would not be anymore "openmpi everywhere but in
these 3 archs" but it'll be "openmpi here and mpich here, period.").
Guess a sourceful upload of mpi-defaults for every new architecture is
feasible and easy to deal with, even if annoying.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature