unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: IDEA: Give Our Generations a Name
Date: Tue, 17 Jan 2023 01:52:24 +0000	[thread overview]
Message-ID: <86mt6h2a1k.fsf@riseup.net> (raw)
In-Reply-To: <9b2e8624e8325f2ff3b4efc88547b2a2@dismail.de>


"jgart" <jgart@dismail.de> writes:

> Hi Guixers,
>
> What do you think if we would be able to give past generations a name?
>
> I'm thinking of the way you can do the following with git:
>
> git stash -m "My description of this important stash."
>
> I think this would help differentiate slight differences that would be
> hard to tell what the state of that generation was by just looking at
> the differences of profile package content.
>
> to bloat? or not to bloat? that is the question

Since generations are just symlinks to profiles in the store and a
profile can be in multiple generations, this would require wrapping the
profile with some additional metadata.  I guess it's technically as
simple as adding a "dummy" package that just contains the name in a file
in output/etc/generation-name.txt or something, that would get unioned
into the profile, and then it's a simple matter of outputting that info
in --list-generations.
Right?
I would actually like this for system profiles quite a lot.  When you're
working on something like a new file-system or service integration and
have some nondeterministic errors and are trying to track down which
generations reproduce it, it's nice to know in what way generation 24 is
different from generations 15 through 23.
(Also it still sucks that we can't have a single generation with
multiple config variants to choose from at boot, but I digress.)


  reply	other threads:[~2023-01-17  2:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 23:40 IDEA: Give Our Generations a Name jgart
2023-01-17  1:52 ` Csepp [this message]
2023-01-18 18:31   ` Liliana Marie Prikler
2023-01-19 11:23     ` Csepp
2023-01-17  8:39 ` Simon Tournier
  -- strict thread matches above, loose matches on Subject: below --
2023-01-17 17:03 Nathan Dehnel

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=86mt6h2a1k.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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).