From: Xinglu Chen <public@yoctocell.xyz>
To: "Andrew Tropin" <andrew@trop.in>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, guix-maintainers@gnu.org
Subject: Re: Return back original implementation for text-config serialization
Date: Sat, 05 Feb 2022 15:43:34 +0100 [thread overview]
Message-ID: <87zgn5e5m1.fsf@yoctocell.xyz> (raw)
In-Reply-To: <87o846y24v.fsf@trop.in>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
Hi,
Andrew schrieb am Donnerstag der 20. Januar 2022 um 16:20 +03:
>>> 2. Looks strange implementation-wise.
>>>
>>> If we want to insert the file path to file-like object for new-style
>>> text-config internally we do something like
>>>
>>> (mixed-text-file ...
>>> "source \" "\n"
>>> #~(read-everything-from-file
>>> #$(computed-file "unecessary-file-name"
>>> #~#$(local-file "blabla.sh"))))
>>
>> When would one write such a thing?
>
> I have very same question :)
>
> It's what happens internally in current implementation, something like
> that goes to home-files-service-type.
From what I can tell, ‘home-files-service-type’ doesn’t seem to have
anything like that. I am not able to find any usages for
‘computed-file’ in Guix Home services either. I am missing something?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2022-02-05 14:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 9:12 Return back original implementation for text-config serialization Andrew Tropin
2022-01-09 11:19 ` Liliana Marie Prikler
2022-01-09 17:48 ` Andrew Tropin
2022-01-09 19:44 ` Liliana Marie Prikler
2022-01-10 9:49 ` Andrew Tropin
2022-01-10 20:12 ` Liliana Marie Prikler
2022-01-12 15:05 ` Andrew Tropin
2022-01-09 12:17 ` Maxime Devos
2022-01-09 12:19 ` Maxime Devos
2022-01-09 17:59 ` Andrew Tropin
2022-01-09 19:00 ` Maxime Devos
2022-01-18 14:26 ` Ludovic Courtès
2022-01-20 13:20 ` Andrew Tropin
2022-01-21 9:30 ` Maxime Devos
2022-01-26 8:34 ` Andrew Tropin
2022-01-27 5:04 ` Maxim Cournoyer
2022-01-28 15:48 ` Andrew Tropin
2022-02-05 11:09 ` Ludovic Courtès
2022-02-13 14:14 ` Andrew Tropin
2022-01-26 8:36 ` Andrew Tropin
2022-02-05 11:34 ` Maxime Devos
2022-02-13 14:09 ` Andrew Tropin
2022-01-24 15:37 ` Ludovic Courtès
2022-01-26 9:11 ` Andrew Tropin
2022-01-26 9:21 ` Andrew Tropin
2022-02-05 14:43 ` Xinglu Chen [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=87zgn5e5m1.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=andrew@trop.in \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
/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).