unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ben Sturmfels <ben@sturm.com.au>
To: guix-devel@gnu.org
Subject: Re: Guix beyond 1.0: let’s have a roadmap!
Date: Fri, 26 Jul 2019 17:00:30 +1000	[thread overview]
Message-ID: <87y30lz3e9.fsf@sturm.com.au> (raw)
In-Reply-To: <877e97vws8.fsf%40gnu.org504D1A97-2EBD-46A1-85B8-091C923DD6A1@vllmrt.net>

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

Sorry, same as Robert, I've lost the original mail.

>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>> [...]
>>
>>> What do *you* want Guix to address in the future?
>>>
>>> #+TITLE: GNU Guix Beyond 1.0—A Road Map

I'd love to be able to annotate user and system generations with some
text, so that the text is shown back to me when running
"--list-generations". For example:

 - "Everything working, don't delete!" or
 - "Testing with CUPS service disabled" or
 - "Excluded Jupyter as build is currently failing" or
 - "Trialing CSVkit"

That way I can look back at `guix package --list-generations` and know
what's I ought to keep or delete. Otherwise all you have is the list of
packages but no information about the intent of each generation.

It would be helpful to be able to do this at the time of creating the
generation and also afterwards.

Regards,
Ben

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2019-07-26  7:00 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 16:05 Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 16:36 ` P
2019-06-27 21:12   ` Ludovic Courtès
2019-06-27 17:06 ` Vagrant Cascadian
2019-06-27 21:17   ` Ludovic Courtès
2019-06-27 18:53 ` Jakob L. Kreuze
2019-06-27 21:18   ` Ludovic Courtès
2019-06-27 19:02 ` Alex Griffin
2019-06-27 22:33   ` swedebugia
2019-06-28  6:11     ` Julien Lepiller
2019-06-28 16:13       ` John Soo
2019-07-01  9:14         ` Ludovic Courtès
2019-07-01 11:57           ` Pierre Neidhardt
2019-07-07 14:15             ` Ludovic Courtès
2019-06-30 13:48   ` Giovanni Biscuolo
2019-07-01  9:16     ` Ludovic Courtès
2019-07-05  7:55       ` Giovanni Biscuolo
2019-07-01 10:05   ` Ludovic Courtès
2019-07-01 13:12     ` Alex Griffin
2019-07-05  8:35       ` Guix UCI comparison (was Re: Guix beyond 1.0: let’s have a roadmap!) Giovanni Biscuolo
2019-07-07 14:09       ` Guix beyond 1.0: let’s have a roadmap! Ludovic Courtès
2019-06-27 19:33 ` Svante Signell
2019-06-27 21:25   ` Ludovic Courtès
2019-06-27 20:28 ` Thompson, David
2019-07-01  9:36   ` Ludovic Courtès
2019-07-01 10:39     ` Hartmut Goebel
2019-07-01  9:37   ` Ludovic Courtès
2019-06-27 22:01 ` Pierre Neidhardt
2019-06-27 22:24 ` Julien Lepiller
2019-07-01  9:48   ` Ludovic Courtès
2019-06-28 16:54 ` znavko
2019-06-28 17:07   ` swedebugia
2019-06-28 17:17   ` znavko
2019-06-29  1:35 ` ison
2019-06-29  4:51   ` pelzflorian (Florian Pelz)
2019-07-01  9:51     ` Ludovic Courtès
2019-06-30 13:13 ` Giovanni Biscuolo
2019-06-30 13:38   ` Robert Vollmert
2019-07-01  9:55     ` Ludovic Courtès
2019-07-05 11:47       ` Robert Vollmert
2019-07-09 10:22         ` Ricardo Wurmus
2019-07-09 10:58           ` Robert Vollmert
     [not found]     ` <877e97vws8.fsf%40gnu.org504D1A97-2EBD-46A1-85B8-091C923DD6A1@vllmrt.net>
2019-07-26  7:00       ` Ben Sturmfels [this message]
2019-07-26  8:27         ` Pierre Neidhardt
2019-08-22 20:59         ` Ludovic Courtès
2019-06-30 13:28 ` Christopher Lemmer Webber
2019-07-01  9:57   ` Ludovic Courtès
2019-07-01 11:47     ` Pierre Neidhardt
2019-06-30 13:59 ` Giovanni Biscuolo
2019-07-01  9:58   ` Ludovic Courtès
2019-07-09 13:32 ` P
2019-07-11 10:11   ` Ricardo Wurmus
2019-07-11 15:17     ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2019-06-28 18:57 Jesse Gibbons
2019-07-01 10:14 ` zimoun
2019-07-01 19:38   ` Jesse Gibbons
2019-07-06 12:50 matias_jose_seco
2019-07-07 14:20 ` 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=87y30lz3e9.fsf@sturm.com.au \
    --to=ben@sturm.com.au \
    --cc=guix-devel@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).