unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>, Csepp <raingloom@riseup.net>,
	 guix-devel@gnu.org
Subject: Re: splitting up and sorting commits?
Date: Fri, 04 Nov 2022 18:53:33 +0100	[thread overview]
Message-ID: <dd0600178355237196dd9a24acc095095ca7046e.camel@gmail.com> (raw)
In-Reply-To: <86bkpn5b4f.fsf@gmail.com>

Am Freitag, dem 04.11.2022 um 10:20 +0100 schrieb zimoun:
> Hi Liliana,
> 
> On Thu, 03 Nov 2022 at 21:59, Liliana Marie Prikler
> <liliana.prikler@gmail.com> wrote:
> 
> >                                                  The pauper's
> > solution would be to keep a separate "scratch pad" file containing
> > a bunch of assorted guix packages, ordered in a way that all
> > packages are defined before they're used as inputs – you can easily
> > maintain this order by insertion sort.
> 
> I did something similar that for some Julia packages, but it can be
> tedious depending on the number of packages.  Well, it could be cool
> to have something like
> 
>     guix graph -m some-packages.scm --sort
> 
> returning the list of packages sorted (topological order).
Sorting packages in files sounds like a good application for guix style
imho.  We might even want different orders like topological or
alphabetical.  Guix graph can aid in that, but it'd return a graph
rather than the raw package code.

Cheers


  reply	other threads:[~2022-11-04 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  0:05 splitting up and sorting commits? Csepp
2022-11-02 14:43 ` zimoun
2022-11-03 20:59 ` Liliana Marie Prikler
2022-11-04  9:20   ` zimoun
2022-11-04 17:53     ` Liliana Marie Prikler [this message]
2022-11-06  9:59 ` Andreas Enge
2022-11-06 12:19   ` Csepp

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=dd0600178355237196dd9a24acc095095ca7046e.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=raingloom@riseup.net \
    --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 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).