From: "Ludovic Courtès" <ludo@gnu.org>
To: 36351@debbugs.gnu.org
Subject: [bug#36351] [PATCH 00/10] Add 'derivation-build-plan', improve (guix derivations)
Date: Mon, 24 Jun 2019 14:18:57 +0200 [thread overview]
Message-ID: <20190624121857.5818-1-ludo@gnu.org> (raw)
Hello Guix,
This is the season cleanup of (guix derivations)!
The initial motivation was to allow ‘show-what-to-build’ to do deal
with builds of single derivation outputs, which became possible in
commit f8a9f99cd602ce1dc5307cb0c21ae718ad8796bb.
I ended up replacing ‘derivation-prerequisites-to-build’ with
‘derivation-build-plan’, which is both more flexible and simpler.
That led me to change <derivation-input> so that it would contain
a <derivation> instead of a derivation file name, which is more
natural and helps for things like ‘derivation-build-plan’ that
traverse the derivation graph (previously it’d have to call
‘read-derivation-from-file’, which would look up the derivation
in ‘%derivation-cache’.)
I wanted to change ‘guix build’ to support things like:
guix build groff:doc
but there are slight complications so I’ll punt on that for now.
Thoughts?
Ludo’.
Ludovic Courtès (10):
derivations: Add 'derivation-input'.
derivations: Rewrite and replace 'derivations-prerequisites-to-build'.
ui: 'show-what-to-build' uses 'derivation-build-plan'.
graph: Use 'derivation-input-derivation'.
derivations: <derivation-input> now aggregates a <derivation>.
derivations: 'derivation' preserves pointer equality.
derivations: 'build-derivations' can be passed derivation inputs.
packages: 'specification->package+output' distinguishes "no output
specified".
ui: 'show-what-to-build' accepts derivation inputs.
ui: 'show-derivation-outputs' accepts <derivation-input> records.
gnu/packages.scm | 8 +-
guix/derivations.scm | 269 +++++++++++++++++++++++------------------
guix/scripts/graph.scm | 3 +-
guix/ui.scm | 67 +++++-----
tests/derivations.scm | 80 ++++++------
tests/grafts.scm | 16 +--
tests/packages.scm | 32 +++++
7 files changed, 271 insertions(+), 204 deletions(-)
--
2.22.0
next reply other threads:[~2019-06-24 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 12:18 Ludovic Courtès [this message]
2019-06-24 12:22 ` [bug#36351] [PATCH 01/10] derivations: Add 'derivation-input' Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 02/10] derivations: Rewrite and replace 'derivations-prerequisites-to-build' Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 03/10] ui: 'show-what-to-build' uses 'derivation-build-plan' Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 04/10] graph: Use 'derivation-input-derivation' Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 05/10] derivations: <derivation-input> now aggregates a <derivation> Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 06/10] derivations: 'derivation' preserves pointer equality Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 07/10] derivations: 'build-derivations' can be passed derivation inputs Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 08/10] packages: 'specification->package+output' distinguishes "no output specified" Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 09/10] ui: 'show-what-to-build' accepts derivation inputs Ludovic Courtès
2019-06-24 12:22 ` [bug#36351] [PATCH 10/10] ui: 'show-derivation-outputs' accepts <derivation-input> records Ludovic Courtès
2019-06-27 9:17 ` bug#36351: [PATCH 00/10] Add 'derivation-build-plan', improve (guix derivations) 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=20190624121857.5818-1-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=36351@debbugs.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).