From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id sI6KLH5oxmUnAgAAe85BDQ:P1 (envelope-from ) for ; Fri, 09 Feb 2024 19:01:34 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id sI6KLH5oxmUnAgAAe85BDQ (envelope-from ) for ; Fri, 09 Feb 2024 19:01:34 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=ksHKJUYF; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=lepiller.eu ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1707501694; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=q39dCRh0h+LA0u8xNUBdbLKYqrrAefIlL6hpS6+KFcw=; b=AsbxEITYxmU1N/YVHWVv3p8vnohsdBVxsv5ChJf27pNdyjCMjUJutcU25AX8DoTyl6k00H TJN0CXxS+yfGfa7JGKYBMJqezNOKmtzeAlegniq/Hbqe4LPQqzmqYhUuCJm0RaX/wtmMDo rpWnGHXTFOsGxyjXec4WcaSrBjOH1g/KPIk7McnzAyJEaGZtHYZtUGLyRAvp28kzAVS6z4 CNN40Z95AYU8tA/P5PK5lKN/3+YrD3G7eMAH98Oaq7nxmnKn4m4THHUVS6ksroNDRUOaOa OBXnoLG5tv7DIVbtChtO1F6XP7FjXEI8RWvYZix3dj3p5j5EqSH34VjuRuMp+A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=ksHKJUYF; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=lepiller.eu ARC-Seal: i=1; s=key1; d=yhetil.org; t=1707501694; a=rsa-sha256; cv=none; b=MbQPO8hqTOpR533OHkNIq81epvHjWY26glFTrpNJ5aKpN9nvBorSsFnaENRrl37k0XQP3h bbJTDoJhHD7PJsnYEezFuYXKOFTr6pOJ7nW6vXS8Fb/HKJfFg4B54SNARI3F8F2+CJO4JN ZVmpCJvEUtZPhghd5iG4iYUY7cdkKV8fVZBEsrGqhgXMRch9m6y/dvRLfXXPxz3EqDZSYz Ky9BN1DgR5nfLuNcLMIeS5sZTeloaIvVNwQoppRWPHuZzVBjI7MhM50que2ZEaSgmcnfsR 9ZpItEDD6bnFGbKx724s54G8u2A7Nt/QnoJWUZUlLPUmQ8DXFSWzC6A2WlZjBg== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7ED056E096 for ; Fri, 9 Feb 2024 19:01:34 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rYVBR-0006yO-5y; Fri, 09 Feb 2024 13:01:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rYVBN-0006xO-J2 for help-guix@gnu.org; Fri, 09 Feb 2024 13:01:02 -0500 Received: from lepiller.eu ([89.234.186.109] helo=hermes.lepiller.eu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rYVBK-0006Zm-Ri for help-guix@gnu.org; Fri, 09 Feb 2024 13:01:01 -0500 Received: from hermes.lepiller.eu (localhost [127.0.0.1]) by hermes.lepiller.eu (OpenSMTPD) with ESMTP id cfb2dc60; Fri, 9 Feb 2024 18:00:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date:from :to:subject:in-reply-to:references:message-id:mime-version :content-type:content-transfer-encoding; s=dkim; bh=cRY2u33IC676 dbmbctBqC3fOEu+psBs7l25nMrgNeIg=; b=ksHKJUYFvaSgb0GMWzHj092pYFuI /SJsWwsT7cwcd0ZoJFFTE1kQXT0AiE+luVGkmQ/ab7w/P50pDFtvUtY/MtUowtrY OYvvuB5tXxpK1ZeFJHA5grcorg8ULxwQXVhEZxgF++TDTMK2jQaYFrSMdvXDfCv8 3EtY0XfGpsjXN9VJ6f/T1r+Oekj6+wtzJvVYr5suXyo+ghODTJSzgvoeqqfe2gH8 yhhXEJhHO82+5xPSxNCtuWPwYRXADs0rwVgB4rTTAZEoyuSTARZwazho84u/3IAC 9ujG8FmW+mhUpa26Wb0DnW+xOjmGU7fl0dh2KzbVdJiTzNuqpcon7un+4Q== Received: by hermes.lepiller.eu (OpenSMTPD) with ESMTPSA id d7301963 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 9 Feb 2024 18:00:50 +0000 (UTC) Date: Fri, 09 Feb 2024 19:00:46 +0100 From: Julien Lepiller To: help-guix@gnu.org, Andy Tai Subject: Re: same package defined in multiple channels? User-Agent: K-9 Mail for Android In-Reply-To: References: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=89.234.186.109; envelope-from=julien@lepiller.eu; helo=hermes.lepiller.eu X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -6.87 X-Migadu-Queue-Id: 7ED056E096 X-Spam-Score: -6.87 X-Migadu-Scanner: mx11.migadu.com X-TUID: q0JoLjjLeG5m Hi Andy, They will all be available, and the one used will depend on the situation = and how you use them=2E Consider 'foo' is not only in different channels, but also in different mo= dules (from the root of the channel, they are defined in different director= ies/files)=2E In that case, all versions are visible=2E From the command line, this is s= imilar to other packages that may have multiple versions in a single channe= l=2E For instance 'guix install foo' will install the package with the grea= test version numbes, fsom any channel=2E 'guix install foo@3' will select t= he one that has the greatest version, with major version starting with 3=2E For dependencies, manifests or other scheme code, the story is different= =2E Say 'bar' in guix depends on foo, and 'baz' in 'mychannel' depends on f= oo=2E The code in guix would have a use-module (gnu packages foo) and use 'foo' = from this module as input for bar=2E It means it is always the guix's foo t= hat is being used to build bar in guix=2E Similarly, mychannel can choose to import (gnu packages foo) and use guix'= s version as dependency in baz, or (mychannel packages foo) to use its own = version of foo=2E The fact that foo is implemented in both channels doesn't replace dependen= cies in other channels: they are independent (unless they explicitly depend= on another channel)=2E Or, are they? Well, if a channel were to redefine the same module as another one, say my= channel defines a gnu/packages/foo=2Escm file, then all definitions in guix= 's foo=2Escm are shadowed (or the other way around depending on channel ord= er) and: - shadowed versions are no longer available on the command line - dependents will use the only one that is visible to scheme, so dependenc= ies can be rewritten that way=2E Hope that makes things a bit clearer :) Le 9 f=C3=A9vrier 2024 09:15:02 GMT+01:00, Andy Tai a = =C3=A9crit=C2=A0: >Hi, I wonder if I have multiple Guix channels, and the same package is >defined in multiple channels, of different versions, what would happen >if I do guix pull? Would the first package definition encountered in >the first channel containing the definition of this package in the >channel list be used, shadowing the other definitions in later >channels? >