From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id IKIzCnM7FmC7GQAA0tVLHw (envelope-from ) for ; Sun, 31 Jan 2021 05:09:07 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id ME4hBnM7FmDzUgAA1q6Kng (envelope-from ) for ; Sun, 31 Jan 2021 05:09:07 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 78AB7940415 for ; Sun, 31 Jan 2021 05:09:06 +0000 (UTC) Received: from localhost ([::1]:52064 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l64yv-0005DL-3c for larch@yhetil.org; Sun, 31 Jan 2021 00:09:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:53286) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l64yI-0004up-2V for guix-devel@gnu.org; Sun, 31 Jan 2021 00:08:26 -0500 Received: from 101c.relay.hey.com ([204.62.115.197]:33671) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l64yE-0003yL-4I for guix-devel@gnu.org; Sun, 31 Jan 2021 00:08:24 -0500 Received: from hey.com (bigip-vip-new.rw-ash-int.37signals.com [10.20.0.24]) by 101.relay.hey.com (Postfix) with ESMTP id 91239A1075; Sun, 31 Jan 2021 05:08:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hey.com; s=heymail; t=1612069700; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=F4z9/KJWmbxJcSuGT+5ldHm3EVwv029KXWFk+6Manlw=; b=PfX3gSUPh1RnrNo+ci5ESVzbMyU6lQNg3vXKafX2B68qABZC56uw/so2Oif5L9kr3S8UgV 5v/FKdRc1C/ymFZ8mwm5hMJl0volxn92B//R30vMLccKNbU/dXNj7YgEvDZCKvHX68K7Kq Pz5SjrbXq1Q+W5EVd33Bgy544CHw8vnph5ZE4UNW9Kpf9oCL4PBebHR5iWPA3r6or2kCcn OyTNqs+dZn9gNpycgnYRBFfTrtf3Rz3bYJPi4wheQTzL37D7Mx+sDimTBaBjuHazaWuYd8 vOpqgh/setFGLVn5yKlwCIMAt89J+rOw67jAXsMIV28V+aSnVliYLzpsZnBd1Q== Date: Sun, 31 Jan 2021 05:08:20 +0000 From: Ryan Prior To: zimoun , =?UTF-8?B?THVkb3ZpYyBDb3VydMOocw==?= Message-ID: <896b9daa9aa2a999e30ab09736679408ebb41d9b@hey.com> In-Reply-To: <87wnvup19d.fsf_-_@gnu.org> Subject: Re: bug#45919: [PATCH 0/8] Exporting a manifest and channels from a profile Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_60163b448d53e_2e9e3020515de"; charset=UTF-8 Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=204.62.115.197; envelope-from=ryanprior@hey.com; helo=101c.relay.hey.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Development of GNU Guix and the GNU System distribution , 45919@debbugs.gnu.org Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -1.05 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=hey.com header.s=heymail header.b=PfX3gSUP; dmarc=pass (policy=quarantine) header.from=hey.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: 78AB7940415 X-Spam-Score: -1.05 X-Migadu-Scanner: scn0.migadu.com X-TUID: wvUmAgBIbDa/ ----==_mimepart_60163b448d53e_2e9e3020515de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On January 30, 2021, "Ludovic Court=C3=A8s" wrote:=0D > Actually, part of the code would be shared anyway, so we could always=0D= > go=0D > with =E2=80=98--export-manifest=E2=80=99 first and think about adding t= he extra files=0D > later. (Though I=E2=80=99m still unsure about these extra files, TBH.)=0D= =0D I do like the extra files. It feels cozy to me, like you have your=0D little profile directory and it has a manifest and a list of channels in=0D= it, that makes it feel more complete. Like having the family pictures on=0D= the wall.=0D =0D The question of what happens if you don't update a profile for a long=0D time and how Guix handles those files moves on is a good one. I think=0D those files should have an indication in there of what version of Guix=0D= was used to produce them, such that you can time-machine back to ensure=0D= you're compatible.=0D =0D I don't think there's much drawback to having both the auto-generated=0D files and a command that generates them. That seems more discoverable -=0D= you might happen across the files when you poke into a profile, or you=0D= might notice the command while reading the docs or the help output.=0D =0D Glad to see this capability land any which way, this is something that=0D= comes up often!=0D =0D While we're considering putting a manifest in the profile, is this a=0D good time to also bring up the idea of renaming the "manifest" file? It=0D= confuses more people all the time. I'd be inclined to rename it=0D "profile-metadata" or "lockfile".=C2=A0=0D ----==_mimepart_60163b448d53e_2e9e3020515de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =0D =0D =0D =0D =0D =0D =0D =0D =0D =0D
=0D
=0D
On January 30, 2021, "Ludovic Court=C3=A8s" <ludo@gnu= .org> wrote:
Actually, part of the code would be shar= ed anyway, so we could always go
with =E2=80=98--export-manifest=E2=80= =99 first and think about adding the extra files
later. (Though I=E2=80= =99m still unsure about these extra files, TBH.)

I d= o like the extra files. It feels cozy to me, like you have your little pr= ofile directory and it has a manifest and a list of channels in it, that = makes it feel more complete. Like having the family pictures on the wall.=

The question of what happens if you don't update a profile for a = long time and how Guix handles those files moves on is a good one. I thin= k those files should have an indication in there of what version of Guix = was used to produce them, such that you can time-machine back to ensure y= ou're compatible.

I don't think there's much drawback to having bo= th the auto-generated files and a command that generates them. That seems= more discoverable - you might happen across the files when you poke into= a profile, or you might notice the command while reading the docs or the= help output.

Glad to see this capability land any which way, this= is something that comes up often!

While we're considering putting= a manifest in the profile, is this a good time to also bring up the idea= of renaming the "manifest" file? It confuses more people all t= he time. I'd be inclined to rename it "profile-metadata" or &qu= ot;lockfile".=C2=A0
=0D
=0D =0D =0D
=0D =0D =0D ----==_mimepart_60163b448d53e_2e9e3020515de--