From: Josselin Poiret <dev@jpoiret.xyz>
To: Maxime Devos <maximedevos@telenet.be>, Csepp <raingloom@riseup.net>
Cc: Ricardo Wurmus <rekado@elephly.net>, guix-devel@gnu.org
Subject: Re: substitute derivation: also substitute grafts?
Date: Mon, 19 Sep 2022 18:26:48 +0200 [thread overview]
Message-ID: <87bkrb8h4n.fsf@jpoiret.xyz> (raw)
In-Reply-To: <eabda289-a8ad-6ef1-8db5-dc8cb401ebd0@telenet.be>
Hi everyone,
Maxime Devos <maximedevos@telenet.be> writes:
> Fallbacks might be necessary (not every store item is constructed from a
> package), but it all sounds doable and efficient. Also the union could
> needs to be modified to ignore the .graft-offsets of the union'ed things.
If I understand the whole thing properly, the daemon already scans for
references and could register their location in the database, avoiding
the need for a potentially brittle in-store format as you highlighted,
although that would require a non-trivial change to both the daemon and
the database format.
In any case, I don't think it's necessary to treat packages in a special
way: any derivation can hold derivations and thus be grafted.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-09-19 16:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 12:58 substitute derivation: also substitute grafts? Ricardo Wurmus
2022-09-15 14:46 ` Csepp
2022-09-15 15:06 ` Maxime Devos
2022-09-15 17:43 ` Csepp
2022-09-15 17:51 ` Maxime Devos
2022-09-19 16:26 ` Josselin Poiret [this message]
2022-09-19 16:57 ` Maxime Devos
2022-09-19 22:00 ` Ricardo Wurmus
2022-10-01 16:43 ` Ludovic Courtès
2022-10-01 17:29 ` Ricardo Wurmus
2022-10-01 18:00 ` Tobias Geerinckx-Rice
2022-10-01 18:27 ` Ricardo Wurmus
2022-10-05 10:03 ` Ludovic Courtès
2022-10-05 11:41 ` zimoun
2022-10-07 22:21 ` Mark H Weaver
2022-10-10 15:32 ` Ludovic Courtès
2022-10-10 15:55 ` zimoun
2022-10-10 17:50 ` Ricardo Wurmus
2022-10-05 12:53 ` Ricardo Wurmus
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=87bkrb8h4n.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--cc=raingloom@riseup.net \
--cc=rekado@elephly.net \
/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).