unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel <guix-devel@gnu.org>
Subject: Storing serialised graph along with packages
Date: Sat, 22 Jul 2017 13:32:23 +0200	[thread overview]
Message-ID: <87a83waerc.fsf@elephly.net> (raw)

Hey Guix,

it always bothered me that after building a package we lose all of the
beautiful features that Guix as a Guile library gives us.  We always
need to keep track of the Guix version at the time of building the
package and only then can we hope to rebuild the same thing again at
some point in the future.

What do you think about storing the serialised subset of the package
graph in a separate output of the package?  Currently, the only place
where we store anything meta is the database.  Wouldn’t it be great if
we could “dump an image” of the state of Guile when it has evaluated the
section of the package graph that is needed to build it?

Then we could just load the serialised state into Guile at a later point
and inspect the package graph as if we had Guix checked out at the given
version.  I suppose we could also store this kind of information in the
database.

I’d really like the graph to stay alive even after Guix has moved on to
later versions.  It also sounds like a really lispy thing to do.

What do you think?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

             reply	other threads:[~2017-07-22 11:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22 11:32 Ricardo Wurmus [this message]
2017-07-23  5:11 ` Storing serialised graph along with packages Catonano
2017-07-23  9:30 ` Ricardo Wurmus
2017-07-23 14:53   ` Ricardo Wurmus
2017-07-23 17:33   ` Jan Nieuwenhuizen
2017-07-24 12:33 ` Ludovic Courtès
2017-07-24 16:43   ` Ricardo Wurmus
2017-07-25  8:14     ` Ludovic Courtès

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=87a83waerc.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@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).