From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Frederickson Subject: =?utf-8?Q?Re:_=E2=80=9CGuix_Profiles_in_Practice=E2=80=9D?= Date: Sun, 3 Nov 2019 11:49:21 -0500 Message-ID: References: <87eeyp597u.fsf@gnu.org> Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <87eeyp597u.fsf@gnu.org> 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: =?utf-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel , help-guix List-Id: help-guix.gnu.org On Nov 3, 2019, at 9:24 AM, Ludovic Court=C3=A8s wrote > Now, this would be very much stateful: you can=E2=80=99t tell in advance w= hether > you=E2=80=99re going to build a new profile based on the current Guix, or > whether you=E2=80=99re going to reuse a previously cached profile that cou= ld be > arbitrarily old. That doesn=E2=80=99t sound great. What if something identifying the profile (directory name? config file?) inc= luded info about the Guix revision it was built from? That way a profile wou= ld be reused if it=E2=80=99s built from the same Guix revision, but if you s= witch revisions it=E2=80=99d be rebuilt. I=E2=80=99m not sure how this would interact with a profile built from packa= ges in multiple channels.=