From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Store channel specification in profile Date: Mon, 09 Dec 2019 18:11:55 +0100 Message-ID: <87tv69bezo.fsf@gnu.org> References: <87blsyelgm.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]:45580) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ieMZk-0002sx-Ix for guix-devel@gnu.org; Mon, 09 Dec 2019 12:12:01 -0500 In-Reply-To: (Konrad Hinsen's message of "Tue, 26 Nov 2019 17:40:48 +0100") 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: Konrad Hinsen Cc: guix-devel@gnu.org Hi! Konrad Hinsen skribis: >> One question arises though: channel specifications only make sense for >> profiles generated with manifests. > > Not even for those, if the manifest uses inferior-packages. I'd go for > per-package channel specifications. They could be optimized (more > compact, more efficiently usable) by first storing a list of all > distinct channels and then a (package . channels) list. This is exactly what=E2=80=99s currently implemented if you look at ~/.guix-profile/manifest, under =E2=80=98provenance=E2=80=99. Like zimoun writes, it would be nice to have some sort of a =E2=80=9Cdescri= be=E2=80=9D command for a regular profile. Actually maybe =E2=80=9Cguix describe -p=E2= =80=9D? Actually =E2=80=98guix describe -p ~/.guix-profile=E2=80=99 works but doesn= =E2=80=99t display anything useful. We could fix that by recognizing the kind of profile, somehow. Thoughts? Ludo=E2=80=99.