From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Store channel specification in profile Date: Tue, 26 Nov 2019 15:55:21 +0100 Message-ID: <87blsyelgm.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53390) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZcLU-0003Mg-3e for guix-devel@gnu.org; Tue, 26 Nov 2019 10:01:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZcFR-0000s6-Gz for guix-devel@gnu.org; Tue, 26 Nov 2019 09:55:26 -0500 Received: from relay5-d.mail.gandi.net ([217.70.183.197]:48977) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iZcFR-0000pz-Am for guix-devel@gnu.org; Tue, 26 Nov 2019 09:55:25 -0500 Received: from bababa (lfbn-1-4156-76.w92-169.abo.wanadoo.fr [92.169.151.76]) (Authenticated sender: pierre@atlas.engineer) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 5A43A1C001E for ; Tue, 26 Nov 2019 14:55:21 +0000 (UTC) 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: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, After the long discussions we had on profile, guix environment, manifest, multi-dimensional rollbacks, etc. I suggest the following fix: let's store the "channel specifications" in the profile / environment, similar to how we store the manifest in etc/manifest. What I call "channel specification" is essentially the output of `guix describe -f channels`. Unless some official term already exists, I propose to document this term in the manual. I propose to store the channel spec under "etc/channel-specification.scm". Or shall we opt for the shorter "etc/channl-spec"? One question arises though: channel specifications only make sense for profiles generated with manifests. What about ad-hoc profiles? Shall we still store the spec in this case? I propose we don't, this could also be a hacky way to check whether a profile is ad-hoc or not. Thoughts? =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl3dPNkACgkQm9z0l6S7 zH+t5gf/QQPsKKyjOnccIKMn+k+zRvbOnKqo3wUfbslKSvU27hG90jOKlGVwkp+t q/xJTrKHLAaoTwOYpqeplc6ob0FEj9DYGmCGm2TjPiMKtXAH2S9wLG1NXCrUCDB4 26KIxrR1LP89XOgd86NBu3pG1ATcCKcWJNhnJvl6gRi/xtHIy/APzGchHlz0Juuw D0EowMatnRLhqpMKp8eKyvrh5eD+xiGiB+QuTFcj7ztngJLUX15Rk5jb1tPUJXo8 avh+9aI9imqC0qrlY9QX+kX81/3m1fnpT1SubEjH/7vOHzO6GItPF8YdK7qDseK9 qbRvaS2S7+gSZTdILak13TO11opIIg== =39yj -----END PGP SIGNATURE----- --=-=-=--