unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: [WIP][PATCH] profiles: info-dir-file: Don't consider unwanted manifest entries
Date: Mon, 18 Dec 2017 10:28:16 +0100	[thread overview]
Message-ID: <87vah4wfkf.fsf@gnu.org> (raw)
In-Reply-To: <87ind8ja9h.fsf@member.fsf.org> ("宋文武"'s message of "Fri, 15 Dec 2017 23:12:10 +0800")

Hello!

iyzsong@member.fsf.org (宋文武) skribis:

> Currently we run profile hooks for all manifest inputs, so if you
> install a new package to your profile, all profile hooks will be run
> again, even if the new package doesn't provide info manuals, man pages,
> etc.  Ideally only interested hooks need to be run, eg: if the new
> package has info manuals, then the 'info-dir-file' hook will run.
>
> I get it works somehow, but breaks the '--dry-run' functionality which I
> have no idea how to preserve...

Indeed.  I had the idea of adding a notion of “build rounds”, which
would also be useful for grafts: you’d register (client-side) an extra
build round to be run after the current one.  For grafts, the first
round would return the ungrafted derivations.  For profile hooks, the
first round would return the profile without any hooks.  “-n” would
display what would be built/downloaded as part of the first round,
ignoring subsequent rounds.

I realize that’s a lot hand-waving, so I’ll have to see if I can get a
proof-of-concept ready in the coming weeks.

Ludo’.

  parent reply	other threads:[~2017-12-18  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15 15:12 [WIP][PATCH] profiles: info-dir-file: Don't consider unwanted manifest entries 宋文武
2017-12-15 15:40 ` Martin Castillo
2017-12-22 11:21   ` 宋文武
2017-12-18  9:28 ` Ludovic Courtès [this message]
2018-01-01 10:37   ` 宋文武

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=87vah4wfkf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@member.fsf.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).