From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Re: Store channel specification in profile Date: Fri, 31 Jan 2020 10:21:56 +0100 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33881) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ixSV2-0008Ca-Vu for guix-devel@gnu.org; Fri, 31 Jan 2020 04:22:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ixSV1-0005Qe-Vy for guix-devel@gnu.org; Fri, 31 Jan 2020 04:22:04 -0500 In-Reply-To: <87zhe4px2a.fsf@ambrevar.xyz> 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: Pierre Neidhardt , zimoun Cc: Guix Devel Hi Pierre, > We've made some progress on the topic during the Guix Days. Thanks for the summary! > The Plan=C2=A9: > > On every profile installation, we generate a "specifications.scm" file al= ongside > the internal "manifest". Sounds good. > Problems: > > - There may be too many provenances, we need to add a CLI flag to > ignore provenance. Too many in what sense? I'd just print a warning if the specification refers to more than, say, five inferiors. Users can then clean up their profile or live with the mess. Cleaning up just means updating the profile. That would re-create specifications.scm, in a better way than a special CLI flag because specifications.scm is always the same as the current profile. > Proposed format for "specifications.scm": we can reuse > `specifications->manifest`. Each entry is either or string, in which cas= e it > acts as before, or a list, with the following self-explanatory elements: Looks good. > A somewhat unrelated propostion: To avoid further confusion between the i= nternal > "manifest" and the user-facing "--manifest", we could rename the internal > manifest to $profile/internal-maifest. Fine, but not so critical. I doubt there are many users who ever look at that file. Cheers, Konrad.