unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 61684@debbugs.gnu.org
Subject: bug#61684: can't compose 'with-patch' with 'with-source'
Date: Fri, 24 Feb 2023 14:43:03 +0100	[thread overview]
Message-ID: <87y1onkwm0.fsf@gmail.com> (raw)
In-Reply-To: <87h6vbgpxf.fsf@gmail.com>

Hi Maxim,

On ven., 24 févr. 2023 at 08:21, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

>> Well, I am not convinced that enforce the ordering is a good thing
>> because as Ludo said, some HPC user exploits this control of ordering to
>> generate complex transformations.
>
> Could we gather more information about that use case?  It needs to be
> clear if we are to constrain the design (solution) by it.

Well, I do not have the details.  Just to mention two presentations
[1,2] exposing how transformations help for them.

1: <https://10years.guix.gnu.org/static/slides/07-swartvagher.pdf>
2: <https://hpc.guix.info/static/doc/atelier-reproductibilit%C3%A9-2021/marek-fel%C5%A1%C3%B6ci-org-guix.pdf>

There they intensively uses transformations.  For instance, p.4 of [2]
it reads,

        guix environment --pure --with-input=pastix-5=pastix-5-mkl \
        --with-input=mumps-scotch-openmpi=mumps-mkl-scotch-openmpi \
        --with-input=openblas=mkl --with-git-url=gcvb=$HOME/src/gcvb \
        --with-commit=gcvb=40d88ba241db4c71ac3e1fe8024fba4d906f45b1 \
        --preserve=^SLURM --ad-hoc bash coreutils inetutils findutils \
        grep sed bc openssh python python-psutil gcvb scab slurm@19 openmpi

For this specific example, the order may or not matter.  The point is
that HPC folks are intensively using transformations and, since the
order currently matters, enforcing one specific order could break their
workflow, and even could make impossible what is currently possible.

Quoting Ludo,

                                                 (this is crucial for our HPC
        users, who routinely combine a whole bunch of options; you have no idea
        how far they go once you give them the tool :-))

        <https://issues.guix.gnu.org/msgid/871qmg79u7.fsf@gnu.org>

and I agree with « you have no idea how far they go once you give them
the tool :-)) ».

For what my opinion is worth. :-)

Cheers,
simon




  reply	other threads:[~2023-02-24 13:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 18:08 bug#61684: can't compose 'with-patch' with 'with-source' Maxim Cournoyer
2023-02-21 19:05 ` Simon Tournier
2023-02-23 14:08 ` Ludovic Courtès
2023-02-23 22:27   ` Maxim Cournoyer
2023-02-24 12:02     ` Simon Tournier
2023-02-24 13:21       ` Maxim Cournoyer
2023-02-24 13:43         ` Simon Tournier [this message]
2023-02-24 13:52           ` Maxim Cournoyer
2023-02-25 12:29             ` Simon Tournier
2023-02-25 19:43               ` Maxim Cournoyer
2023-02-27 14:12             ` Ludovic Courtès
2023-02-27 16:29               ` Maxim Cournoyer
2023-02-27 14:09       ` Ludovic Courtès
2023-02-28 10:00         ` Simon Tournier
2023-03-01 15:49           ` Ludovic Courtès
2023-02-24 13:59   ` Maxim Cournoyer
2023-03-03  9:43     ` 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=87y1onkwm0.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=61684@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).