From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: help-guix <help-guix@gnu.org>
Subject: running a script in a post-build hook?
Date: Fri, 7 Oct 2016 17:18:36 +0200 [thread overview]
Message-ID: <877f9kfar7.fsf@mdc-berlin.de> (raw)
Hi Guix,
here’s my problem: I need to have the store on a big slow NFS server
with online compression and deduplication. This means that *everything*
in Guix is slow: downloading binaries, building packages from source,
building a new profile generation — it’s all *very* slow.
So I thought: I should be able to just have the store on fast local
disks and copy over store items to the slow NFS server when they are
done. This is not easy because the store is very big and at the
filesystem level we cannot take advantage of the fact that the store is
append-only for the most part. So running rsync, for example, won’t cut
it.
The daemon, however, does have information about completed builds and
new store items. Does the daemon have a post-build hook that can be
called with the names of the new store items which I could then copy
over? (Or even the names of store items I need to delete after “guix
gc”.)
Could the build hook feature be used for this, maybe by wrapping the
normal build such that a script is run when it finishes?
Finally, is this a good idea? Or is /gnu/store/.links going to be a
problem? Should a post-build hook also inform about deduplication
decisions? Or should I just turn of deduplication in my case?
~~ Ricardo
next reply other threads:[~2016-10-07 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 15:18 Ricardo Wurmus [this message]
2016-10-07 19:42 ` running a script in a post-build hook? Ludovic Courtès
2016-10-13 11:33 ` Ricardo Wurmus
2016-10-13 19:50 ` 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=877f9kfar7.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=help-guix@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.
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).