unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Juliana Sims <juli@incana.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 69313@debbugs.gnu.org
Subject: [bug#69313] [PATCH v2 0/2] gnu: tlpui: Fix location for "defaults.conf".
Date: Tue, 27 Feb 2024 12:10:47 -0500	[thread overview]
Message-ID: <ZDYI9S.PC6SWWBGLP8T3@incana.org> (raw)
In-Reply-To: <87edd3d41p.fsf@nicolasgoaziou.fr>



> I'm dubious about the "code modernization" part. ... IIUC, the
> `file-append' way makes it more difficult to use package
> transformations, since you basically bind the executables to a fixed
> package.

I used the phrase "modernization" just because `file-append` is a 
g-expression-related procedure, and my understanding is that gexprs are 
the new way to do things. I hadn't considered the 
fixing-to-specific-packages aspect. In theory one could bind a 
replacement package to the same name in the scope of g-expression 
expansion (package parameterization, for example, will enable this more 
simply if and when it's done), but that's kind of hacky atm and 
shouldn't be a burden on anyone inheriting from this package. I now 
understand why one might prefer `search-input-file` and, furthermore, 
think it should be preserved.

If no one else has input on this in the next couple days, I'll try to 
remember to close this issue soon :)

Thanks for helping me think about something in a new way!

-Juli






  reply	other threads:[~2024-02-27 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 20:10 [bug#69313] [PATCH] gnu: tlpui: Fix broken package Juliana Sims
2024-02-22 22:07 ` Nicolas Goaziou via Guix-patches via
2024-02-22 22:56   ` [bug#69313] [PATCH v2 0/2] gnu: tlpui: Fix location for "defaults.conf" Juliana Sims
2024-02-23  7:37     ` Nicolas Goaziou via Guix-patches via
2024-02-27 17:10       ` Juliana Sims [this message]
2024-02-22 22:56   ` [bug#69313] [PATCH v2 1/2] " Juliana Sims
2024-02-22 22:56   ` [bug#69313] [PATCH v2 2/2] gnu: tlpui: Reference inputs directly during build Juliana Sims

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=ZDYI9S.PC6SWWBGLP8T3@incana.org \
    --to=juli@incana.org \
    --cc=69313@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).