Bug#814943: mpi-default-dev: provide the list of architectures for each MPI implementation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Mattia, Le 27/02/2016 12:29, Mattia Rizzolo a écrit : >> The feature that I would need for e.g. the yorick package is the >> list of architectures on which each implementation is available. >> This is what I currently check and hardcode by hand. I guess this >> is also what other people do when they provide packages with >> distinct names for each flavour. Yes, it is certainly loosing of its usefulness... > Guess I can do that too. I personally think it's kind of pointless > as of now, where mpich is available everywhere and openmpi is > available on all but m68k (not considering powerpcspe that > yesterday has been resurrected from ashes…) > > Anyway, What about: > > https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.g it/commit/?id=57d37c200258e7512733d7ee36aade8bf806ffea > > ? Perfect, thanks. > I do think this is a bigger improvment than hardcoding this in a > donzen of packages, everyone with its own data source. > -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJW1BQXAAoJEJOUU0jg3ChAR5cQAK8oGwvRameitL5ZMiVAAAki LzJNYaBUJIupsg5/WsUyd/4arzJOkXPaWOOyWCyo5f79DjEXmYXfC/9oZsZXIKtu 0XJUZQFVS9UaieWhPRLTDcUbEA77wSCl8qOgpRDtPPdVgN69au6RajKe8TPx87GY BJVrvO+4du3P9hN8PcXCg/dIrxJ+LI88iURPzFPlbsT4THokH1Z4YwkuVPkNXRxp 4t3XOjcPLYa4V5IBJZGCbQ02xXyzsdHGYid3IDlLhGAHO59jK68IHAGlwa48eZrw eR7e+zOwmA14+ViEqD24DgQU8yOCgZDVU5kGTZ4yDXLWatZdp+9yV4AKr/UNOFoI yPYFmSI55ooOtydIJwwzIOMMhrzAn4t90m7nfJXCqkw3zRsRiZb8LBnzL5TvUQR8 92rgElndITHA+QXBCkdGqNaeHKGi6wTRHdy030UTOlqUglfUUaQLpQGto7NbPm93 7l6SwKwTiMS+J/BxAyMt9rqAUpj2YyNkpwGVHRdue8EByTAWnQV2X6ksrBpHK81w RNSHUkn3a4ydKr4YJO2NlyNl+m7fuhu4J3gd+2JMaApuJAL6dSYaZJ7BSvLYm31m RYQB8s9ux6ikqKIjRA4dKjsbgEqqqNCzrb5rRrxAgoy70mecJBx/EuMR7ibKSu2z Kvprrazm7EM7zLuhxR73 =OgYk -END PGP SIGNATURE- -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#814943: mpi-default-dev: provide the list of architectures for each MPI implementation
Sorry for the late reply, I got sucked in RL stuff… On Tue, Feb 16, 2016 at 10:19:06PM +0100, Thibaut Paumard wrote: > It has been discussed in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813128 > that some MPI packages build in two flavours (openmpi and mpich) and > need to know at upload time for which architecture each implementation > is available. > > It has been proposed to add two variables to > /usr/share/mpi-default-dev/debian_defaults for this purpose. > > Last iteration of this discussion below. > > Mattia, it looks like there is a misunderstanding: in your commit, > OPENMPI_ARCHITECTURES and MPICH_ARCHITECTURES only list the > architectures for which each implementation is the default. Yes. > The > feature that I would need for e.g. the yorick package is the list of > architectures on which each implementation is available. This is what > I currently check and hardcode by hand. I guess this is also what > other people do when they provide packages with distinct names for > each flavour. Guess I can do that too. I personally think it's kind of pointless as of now, where mpich is available everywhere and openmpi is available on all but m68k (not considering powerpcspe that yesterday has been resurrected from ashes…) Anyway, What about: https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.git/commit/?id=57d37c200258e7512733d7ee36aade8bf806ffea ? I do think this is a bigger improvment than hardcoding this in a donzen of packages, everyone with its own data source. -- 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 `- signature.asc Description: PGP signature -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#814943: mpi-default-dev: provide the list of architectures for each MPI implementation
Package: mpi-default-dev Version: 1.2 Severity: wishlist It has been discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813128 that some MPI packages build in two flavours (openmpi and mpich) and need to know at upload time for which architecture each implementation is available. It has been proposed to add two variables to /usr/share/mpi-default-dev/debian_defaults for this purpose. Last iteration of this discussion below. Mattia, it looks like there is a misunderstanding: in your commit, OPENMPI_ARCHITECTURES and MPICH_ARCHITECTURES only list the architectures for which each implementation is the default. The feature that I would need for e.g. the yorick package is the list of architectures on which each implementation is available. This is what I currently check and hardcode by hand. I guess this is also what other people do when they provide packages with distinct names for each flavour. Kind regards, Thibaut. Le 16/02/2016 19:37, Mattia Rizzolo a écrit : > On Tue, Feb 16, 2016 at 11:37:19AM +0100, Thibaut Paumard wrote: >>> 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. > > See > https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.g it/commit/?id=07ef8a6 > > https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.git /commit/?id=4fa28c2 > https://anonscm.debian.org/cgit/debian-science/packages/mpi-defaults.g it/commit/?id=d9656b2 > > >> So, what we want if to render RC buggy some packages that need a >> source upload whenever OPENMPI_ARCHITECTURES or >> MPICH_ARCHITECTURES change. > > Somebody needs to do that. I can also have mpi-defaults provide a > script to be called by the packages at build time, if somebody > provides it. > >> 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~) > > umh, looks messy. > >> 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 > > in the past mpi-defaults was binNMUed to change defaults; don't > rely on that. > >> Actually a versioned dependency seems required anyway since you >> know your new package will FTBFS with earlier versions of >> mpi-default-dev. > > *shrugs* > >> 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? > > indeed. probably better suited for a mpi-defaults bug; feel free to > open one and report a summary of what said here. > -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
