all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 61684@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#61684: can't compose 'with-patch' with 'with-source'
Date: Wed, 01 Mar 2023 16:49:33 +0100	[thread overview]
Message-ID: <87pm9sbhf6.fsf@gnu.org> (raw)
In-Reply-To: <87y1oijejb.fsf@gmail.com> (Simon Tournier's message of "Tue, 28 Feb 2023 11:00:08 +0100")

Hi,

Simon Tournier <zimon.toutoune@gmail.com> skribis:

>  1. From my point of view, the transformations are functions that you
>     compose.  The composition rule is not commutative maybe neither
>     associative.  Writing down how each function (transformation)
>     composes with the others allows to specify the composition rules.
>
>  2. All the code in (guix transformations) acts at the package level, so
>     I am still missing why it would not be possible to detect some
>     issues there.

Please check out ‘package-input-rewriting’ and its behavior
with #:deep? #t.  Design discussion: <https://issues.guix.gnu.org/43578>.

>  1. it would not be possible to check if the transforms compose well;
>     somehow verify the assumption.

Try it.  :-)  I tried to explain it multiple times, I really did, but I
guess there’s no substitute to first-hand experience.

> For instance, ’package-with-upstream-version’ raises many warnings
> depending on various cases, and I miss why,
>
>  2. it would not be possible to have similar warnings for other
>     transformations.

‘package-with-upstream-version’ raises warnings that depend exclusively
on local knowledge.

Here we’re talking about warnings related to the composition to two
different options which, like you wrote, are independent functions.
It’s not similar.

HTH!

Ludo’.




  reply	other threads:[~2023-03-01 15:50 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=87pm9sbhf6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=61684@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=zimon.toutoune@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.