On Mon, Feb 15, 2016 at 07:02:06PM +0100, Matthias Klose wrote:
> well, even if you need to have these hard-coded, then have a control.in
some do (blacs-mpi for example).
> generating a control file, and fails when the control file changes. So you
> regenerate it during the build, but fail if it changes.
that's something that should be done. very similarly to several
postgres packages.
> 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.
maybe packages could check whether the architecture they are building
for mismatch against ARCH_DEFAULT_MPI_IMPL before anything.
--
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