From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: Re: Store channel specification in profile Date: Tue, 26 Nov 2019 17:40:48 +0100 Message-ID: References: <87blsyelgm.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38831) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZdtX-0003wS-TZ for guix-devel@gnu.org; Tue, 26 Nov 2019 11:40:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZdtW-0003ea-OP for guix-devel@gnu.org; Tue, 26 Nov 2019 11:40:55 -0500 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]:37751) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iZdtW-0003dj-BQ for guix-devel@gnu.org; Tue, 26 Nov 2019 11:40:54 -0500 In-Reply-To: <87blsyelgm.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.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt , guix-devel@gnu.org Hi Pierre, > 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. Cheers, Konrad