unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully <bjc@spork.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 42164@debbugs.gnu.org
Subject: bug#42164: Combining file-append with gexps results in incomprehensible errors
Date: Sun, 24 Apr 2022 19:27:11 -0400	[thread overview]
Message-ID: <87bkwqqckg.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <5be60a6138fde8bfe521e7e9c7c18f28a9c50742.camel@telenet.be>

Maxime Devos <maximedevos@telenet.be> writes:

> Nowhere.  I tried implementing 'output', and noticed I just 
> ended up
> with something equivalent to a simple call to 'gexp-input' 
> (hence,
> ‘this thing already exists’).  'gexp-input' can be found in 
> (guix
> gexp).

	I finally had a chance to mess around with this, and it 
	does, indeed, do the job. Since it wasn’t clear to me how 
	it worked, I’d like to document it here.

	To accomplish the goal at the begging of this thread, 
	rather than using:
--8<---------------cut here---------------start------------->8---
(file-append #~#$gcc:lib “/lib”)
--8<---------------cut here---------------end--------------->8---

	The “correct” way is this:
--8<---------------cut here---------------start------------->8---
(gexp-input (file-append gcc "/lib") "lib")
--8<---------------cut here---------------end--------------->8---

	The name seems a little weird, since we’re selecting an 
	output, but it makes sense from the other end: we’re 
	creating an input for the higher-level expression (in this 
	case, the special-file-services-type).

	Anyway, this works for me, so this ticket can probably be 
	closed.

-bjc




  reply	other threads:[~2022-04-24 23:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 12:00 bug#42164: Combining file-append with gexps results in incomprehensible errors Jakub Kądziołka
2021-04-13  1:58 ` Maxim Cournoyer
2022-04-23 16:03 ` Brian Cully
2022-04-23 17:06   ` Maxime Devos
2022-04-23 17:29     ` Brian Cully
2022-04-23 18:38       ` Maxime Devos
2022-04-23 20:40         ` Brian Cully
2022-04-23 21:07           ` Maxime Devos
2022-04-24 23:27             ` Brian Cully [this message]
2022-04-25  6:20               ` Maxime Devos

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=87bkwqqckg.fsf@ditto.jhoto.spork.org \
    --to=bjc@spork.org \
    --cc=42164@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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).