unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Maurice Brémond" <Maurice.Bremond@inria.fr>, 39588@debbugs.gnu.org
Subject: [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich
Date: Thu, 15 Oct 2020 21:50:00 +0200	[thread overview]
Message-ID: <861rhz1d7b.fsf@gmail.com> (raw)
In-Reply-To: <87eeupd3t1.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 20 Feb 2020 10:08:10 +0100")

Hi,

Reliving the openmpi->mpich topic of #39588 [1].

1: <http://issues.guix.gnu.org/issue/39588>


On Thu, 20 Feb 2020 at 10:08, Ludovic Courtès <ludo@gnu.org> wrote:

>> Well, for these particular patches, the variants are ok.
>> But we should think about how to ease the variant generation of all the chain.
>
> Well again there are things like ‘package-input-rewriting’ that could
> help: we could define a ‘package-with-mpich’ procedure.

Now the “#:deep?” exists, does it make sense to implement this
“package-with-mpich” procedure?  It could be helpful for HPC people,
isn’t?


All the best,
simon




  parent reply	other threads:[~2020-10-15 19:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 10:44 [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich Maurice Brémond
2020-02-17 17:26 ` Ludovic Courtès
2020-02-17 18:20   ` zimoun
2020-02-20  9:08     ` Ludovic Courtès
2020-02-20 10:23       ` zimoun
2020-02-21  8:03         ` Ludovic Courtès
2020-02-21  8:40           ` zimoun
2020-02-25 16:41         ` zimoun
2020-10-15 19:50       ` zimoun [this message]
2020-10-16  9:32         ` Ludovic Courtès
2020-10-16 11:46           ` zimoun
2020-10-19 13:46             ` Maurice Brémond
2020-10-20 20:55               ` Ludovic Courtès
2020-10-23  9:33                 ` Maurice Brémond
2020-10-23 15:26                   ` Ludovic Courtès
2020-10-23 17:04                     ` Maurice Brémond
2020-11-02 14:02                       ` bug#39588: " Ludovic Courtès
2020-10-21 14:43               ` [bug#39588] (off-topic) double time-machine explanations zimoun
2020-10-23  8:41                 ` Maurice Brémond
2020-02-18 17:58   ` [bug#39588] gnu: Add mpich, scalapack-mpich, mumps-mpich, pt-scotch-mpich, python-mpi4py-mpich Maurice Brémond
2020-02-18 18:22     ` zimoun
2020-02-19 11:45       ` Maurice Brémond
2020-02-19 12:11         ` zimoun
2020-02-19 13:34     ` zimoun
2020-02-21  9:01       ` Maurice Brémond
2020-02-20  9:38     ` Ludovic Courtès
2020-02-21  8:46       ` Maurice Brémond
2020-02-21 11:32         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861rhz1d7b.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=39588@debbugs.gnu.org \
    --cc=Maurice.Bremond@inria.fr \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).