unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rutherther <rutherther@ditigal.xyz>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] qt-build-system: Wrap with build variables to allow %outputs in arguments
Date: Thu, 05 Dec 2024 08:35:56 +0100	[thread overview]
Message-ID: <87jzcepoo3.fsf@ditigal.xyz> (raw)
In-Reply-To: <87ed2m8xfh.fsf@protonmail.com>


Hi John,
thanks.

> You should be able to use gexps, e.g. #$output (see
> <https://guix.gnu.org/manual/devel/en/html_node/G_002dExpressions.html>
> for more details). That is actually the preferred way now, though
> there are still instances of assoc-ref.

> I believe the commit in question is
> <https://git.savannah.gnu.org/cgit/guix.git/commit?id=7d873f194ca69d6096d28d7a224ab78e83e34fe1>.

I've seen this commit before and saw that many of the build systems
in it had the inputs and outputs build variables added, so that's why I asked.

> Though perhaps you are getting at that you'd expect the older way to
> still work? Perhaps qt-build purposefully left the older procedure
> behind as it should have much fewer dependents (which may rely on the
> old assoc-ref)?

Yes, exactly, I wanted to know if this is purposefully left out, ie. for
the thing you are saying - less dependants, or if it was sort of a
mistake.

So is the goal to port everything to gexps eventually, and to get
rid of %outputs completely? 

Regards,
Rutherther


      reply	other threads:[~2024-12-05  7:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 22:17 [PATCH 0/1] qt-build-system: Wrap with build variables to allow %outputs in arguments Rutherther
2024-12-05  6:18 ` John Kehayias via Development of GNU Guix and the GNU System distribution.
2024-12-05  7:35   ` Rutherther [this message]

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=87jzcepoo3.fsf@ditigal.xyz \
    --to=rutherther@ditigal.xyz \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.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).