From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Store channel specification in profile Date: Tue, 25 Feb 2020 11:32:20 +0100 Message-ID: <87imjvarez.fsf@ambrevar.xyz> References: <87blsyelgm.fsf@ambrevar.xyz> <87tv69bezo.fsf@gnu.org> <87zhg1xvmo.fsf@ambrevar.xyz> <874kx8gxh1.fsf@ambrevar.xyz> <87blreasgd.fsf@ambrevar.xyz> <87pnfpsgfx.fsf@gnu.org> <87a76rqu5j.fsf@ambrevar.xyz> <877e1vqowd.fsf@ambrevar.xyz> <87zhe4px2a.fsf@ambrevar.xyz> <87wo91p9yt.fsf@gnu.org> <87eev8gewx.fsf@ambrevar.xyz> <87pneq140d.fsf@gnu.org> <8736bldmzr.fsf@ambrevar.xyz> <87zhdp2p16.fsf@gnu.org> <87imkdky1w.fsf@ambrevar.xyz> <87ftf0j6zq.fsf@gnu.org> 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]:34840) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j6XVt-0007ZG-4z for guix-devel@gnu.org; Tue, 25 Feb 2020 05:32:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j6XVp-0000dI-5R for guix-devel@gnu.org; Tue, 25 Feb 2020 05:32:28 -0500 In-Reply-To: <87ftf0j6zq.fsf@gnu.org> 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-mx.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix Devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ludovic Court=C3=A8s writes: > (Note: we should remove the =E2=80=98sort=E2=80=99 call here as the order= of packages in > the manifest is significant when there are file collisions.) But the export is not an "internal manifest", it should not need to know about package order, right? I sorted the export so that it produces a reproducible output, which is more version-control friendly. > How does that sound? Would you like to integrate something like this, > maybe =E2=80=98guix package --export=E2=80=99 or something? While it would be good to have it, what I was suggesting is that we automatically generate this export on every profile generation, just like we do with system profiles and =2D-8<---------------cut here---------------start------------->8--- /run/current-system/configuration.scm /run/current-system/channels.scm =2D-8<---------------cut here---------------end--------------->8--- I didn't understand from your previous message which downside you find to embedding the specifications.scm file. It would save efforts to the user and be more systematic, in the sense that it gives a guarantee to the user that a specifications.scm corresponds to a profile. This last point, I believe, is crucial. Cheers! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAl5U97QACgkQm9z0l6S7 zH/h7ggAjHtclg66+/ovFmOds0kzfq3dkGYGUPwH29kt/hlhXGyRBnEHeI1FFuUL u/RaFaaJ4PSUs1yGLPRMEG5K4Ei5XdyA8DfU0VFBdqudnWpy8pIvD+cccF4KkyPg mZWMPBf+iDo/w19y3Tmg7nnGV6DcSPf8VxBwLWiNqgq6/wvSaYeUGCqceTNQCM5w hs/2s/iVxdFJwaqJGk+Qafm4wTYaXJ2Ya3CC8Im0b9fDUg/kgTlY7AsUsb8s7074 jXKsMjOaWoC5+/08oldyCX5tMHge7U0HD28R0k1Vz+SnmC5aJYQtfqW/XHmwIjJw 5zzCTL+usbmgpk5tNWeVVzf8fO4E5Q== =DVre -----END PGP SIGNATURE----- --=-=-=--