From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Add the git commit id to the generation information Date: Tue, 30 May 2017 17:48:56 +0200 Message-ID: <87bmqa2vmf.fsf@gnu.org> References: <87k24y4te6.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50829) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dFjOI-0003FE-M0 for guix-devel@gnu.org; Tue, 30 May 2017 11:49:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dFjOE-0002oy-P3 for guix-devel@gnu.org; Tue, 30 May 2017 11:49:02 -0400 In-Reply-To: (Roel Janssen's message of "Tue, 30 May 2017 11:21:53 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Roel Janssen Cc: guix-devel@gnu.org Roel Janssen skribis: > Ricardo Wurmus writes: > >> Hi Roel, >> >>> I have a feature request. >>> >>> When I run 'guix pull', install a package, run 'guix pull' again (on >>> another day), and install another package, I'd get two generations: >>> >>>> Generation 181 May 22 2017 11:47:37 >>>> + haunt 0.2.1 out /gnu/store/x2bkpzrdbaxavl29r2xg0fip1jj= ici9q-haunt-0.2.1 >>>> >>>> Generation 182 May 24 2017 09:52:06 (current) >>>> + guile-commonmark 0.1 out /gnu/store/k8vq65czfb8k4hvvjvs= ca34scd9xsxik-guile-commonmark-0.1 >>> >>> Now, if I'd like to go to the Guix packages source code of generation >>> 181, I can only guess at which actual state of the Guix repository this >>> was, because this timestamp is the timestamp of creating the generation, >>> not the timestamp of the Guix package state. So, I'd like to propose to >>> add the commit id to the generation like so: >>> >>>> Generation 181 May 22 2017 11:47:37 (ae548434337cddf9677a4cd52b937= 0810b2cc9b6) >>>> + haunt 0.2.1 out /gnu/store/x2bkpzrdbaxavl29r2xg0fip1jj= ici9q-haunt-0.2.1 >>>> >>>> Generation 182 May 24 2017 09:52:06 (current) >>>> + guile-commonmark 0.1 out /gnu/store/k8vq65czfb8k4hvvjvs= ca34scd9xsxik-guile-commonmark-0.1 >> >> What would be the expected behaviour in the presence of >> GUIX_PACKAGE_PATH? I could have had GUIX_PACKAGE_PATH set pointing to a >> module containing a custom variant of haunt. >> >> I do agree that it would be very useful to know more about the state of >> Guix for any given generation. However, that state is more complex than >> a single commit. > > Oh, indeed.. Any suggestions? I think this is one of the things that channels mean to address. As a first step, once =E2=80=98guix pull=E2=80=99 uses Guile-Git, we can at= least record the commit of Guix. Ludo=E2=80=99.