all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	Mathieu Othacehe <othacehe@gnu.org>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	73948@debbugs.gnu.org, Christopher Baines <guix@cbaines.net>
Subject: [bug#73948] [PATCH 0/2] 'derivation-build-plan' returns builds in topological order
Date: Wed, 06 Nov 2024 10:11:46 +0100	[thread overview]
Message-ID: <87r07o3ewd.fsf@gnu.org> (raw)
In-Reply-To: <cover.1729603127.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Tue, 22 Oct 2024 15:21:05 +0200")

Ludovic Courtès writes:

Hi,

> There’s one situation in ‘cuirass remote-worker’ where I found that it
> would be more convenient for ‘derivation-build-plan’ to return the list of
> builds in topological order, so a worker can perform them sequentially
> in the right order.
>
> From a UI viewpoint, it also seems to make more sense to display the
> list of things to build in topological order.
>
> Thoughts?

LGTM, and lovely.

Having this sorted would be a big help, I'm often trying to figure this
out by traversing drvs!

-- 
Janneke Nieuwenhuizen <janneke@gnu.org>  | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com




  parent reply	other threads:[~2024-11-06 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 13:21 [bug#73948] [PATCH 0/2] 'derivation-build-plan' returns builds in topological order Ludovic Courtès
2024-10-22 13:22 ` [bug#73948] [PATCH 1/2] derivations: ‘derivation-build-plan’ " Ludovic Courtès
2024-10-22 13:22 ` [bug#73948] [PATCH 2/2] ui: ‘show-what-to-build’ displays " Ludovic Courtès
2024-11-06  9:11 ` janneke [this message]
2024-11-12 23:03   ` bug#73948: [PATCH 0/2] 'derivation-build-plan' returns " Ludovic Courtès
2024-11-16  7:18     ` [bug#73948] " Simon Tournier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r07o3ewd.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=73948@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.