Ludovic Courtès writes: > Roel Janssen <r...@gnu.org> skribis: > >> Ludovic Courtès writes: > > [...] > >>> I don’t think so. The old behavior will always be available by >>> specifying a single generation anyway: >>> >>> guix package --list-generations=42 >>> >>> It may be worth mentioning this in the manual. >>> >>> My understanding of the discussion referred above is that people were >>> fine with that (or indifferent ;-)). >> >> Then the following patch should be it. I applied your genius >> suggestions of using @code{display-entry} instead of >> @code{display-entries}. I learned something new again today. :-) > > Heh. :-) > >>>From 5630a512f16c6677fd5b0b8085e2ef15cb10499b Mon Sep 17 00:00:00 2001 >> From: Roel Janssen <r...@gnu.org> >> Date: Wed, 19 Oct 2016 23:38:11 +0200 >> Subject: [PATCH] guix package: Display generation diffs. >> >> * guix/ui.scm (display-profile-content-diff): New variable. >> * guix/scripts/package.scm (process-query): Use display-profile-content-diff. > > The code LGTM, but it doesn’t implement the behavior I suggested above > for --list-generations=42, which I think I didn’t explain correctly. > > I think what I’m suggesting is that the first matching generation should > be displayed in full using ‘display-profile-content’, and subsequent > generations would be displayed as a diff. > > Thus, when viewing a single generation, as with --list-generations=42, > we’d only display the full contents of that generation. > > Does that make sense?
Ah, sorry, I forgot about this. This makes sense. But then, what should we see when we do: guix package --list-generations=42,46 Should we see: Generation 42 ...: <full contents> Generation 46 ...: <diff with 42> Or should we then see: Generation 42 ...: <full contents> Generation 46 ...: <full contents> Kind regards, Roel Janssen