From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id wLFpAQDzxmP9ZQEAbAwnHQ (envelope-from ) for ; Tue, 17 Jan 2023 20:12:00 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id 2NB4AQDzxmN9eAAA9RJhRA (envelope-from ) for ; Tue, 17 Jan 2023 20:12:00 +0100 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 E2AD8F2BA for ; Tue, 17 Jan 2023 20:11:59 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHr1Y-0005Xb-Qf; Tue, 17 Jan 2023 13:49:32 -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 1pHr1W-0005Wn-8L for guix-devel@gnu.org; Tue, 17 Jan 2023 13:49:30 -0500 Received: from mail-wr1-x42a.google.com ([2a00:1450:4864:20::42a]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pHr1U-0001j1-Ie; Tue, 17 Jan 2023 13:49:30 -0500 Received: by mail-wr1-x42a.google.com with SMTP id b5so10429632wrn.0; Tue, 17 Jan 2023 10:49:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date:message-id :reply-to; bh=ruIQMNHj3ClC+egCVerWeFPXZqHMOH5FysYc76zCQRA=; b=bqwFziF+1chxIA8PQA1zUMwYAQ51PbSGYBDRQXST09bxrvypkmp7QwTsF32H6jn/Yl mxaT+tPMghjphDn0LSmF+TeN/Yo7YekbcP/9Pf6IlL63ko5N5dhOOEiPQIai5vh5fnsI NpDV5ENOJaqAp4SCXKgRt8y0POJ8SnZ+Zz8KKEfvpURZM96+lQfYOQYwQf3XFoz3e4CA KOight3AKdRMdtIbUcPjMTgaQYzIcPw6Tlhy4wZhdr1nTDVXu/IiD4fk/XnVQwoKN/RT DQmv3kLJ8LwLoQ+oAwr2i7wdsgZJgn87izZx2CxNxFJmR8pBqUu7skVYT3NUYg7BP/KW /nXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ruIQMNHj3ClC+egCVerWeFPXZqHMOH5FysYc76zCQRA=; b=ObvErJxoYQTV0sTsd94FkGQ3yCe2A0mKyDR5QIj0IM9hlTmeZRDMNLPrHTNfHCmLZ2 hh5dqeV+SpUHhY+WkozaU8RVynHj/2fL4eDPtxQKqI1XHRYp/iHdi25vXpW80oDBLd5o e47WXEZF2dBXaPWyufvC6OsO2ynmG3cQIHKFZrp9dXza5w/A06NxhXxvEJkkebfWBOlr GUXoq1BjCjtV9++mIyrC3mmrJp/RN8k2jyCPk18C1J5snuG75+2NCDwuUbhoYIA6Apn0 qTxNUGd61IXad4Gu8AV49f9BJ2Qi/WuHDL4ixdMFe7Rlfz39MTyrdIJN414UpvJ9jm1M Rrkw== X-Gm-Message-State: AFqh2kowjVXO/97JY3TI7DlBdUIEew25JXh26vQF8oUWlbgaFvLtnFsV uwajd0AqZ+kTlRqYypVs6T6WMfk2Y1Y= X-Google-Smtp-Source: AMrXdXs6Ihb8EDd6ucLi/i3Gn64evhbxMY3kbMCPBuqfGgraRWrh55vo7y5L5wQx8tpBxnANYvzNyQ== X-Received: by 2002:a5d:6084:0:b0:27a:d81:1136 with SMTP id w4-20020a5d6084000000b0027a0d811136mr656252wrt.7.1673981365648; Tue, 17 Jan 2023 10:49:25 -0800 (PST) Received: from pfiuh07 ([193.48.40.241]) by smtp.gmail.com with ESMTPSA id o2-20020a5d58c2000000b002bdbead763csm18530747wrf.95.2023.01.17.10.49.25 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Jan 2023 10:49:25 -0800 (PST) From: Simon Tournier To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: Guix Devel , Lars-Dominik Braun Subject: Re: properties for default version? (was bug#60200: Incompatibilities between gcc-toolchain and R packages) In-Reply-To: <87v8l5dtxv.fsf@gnu.org> References: <86pmbk3hci.fsf@gmail.com> <87v8l5dtxv.fsf@gnu.org> Date: Tue, 17 Jan 2023 19:48:51 +0100 Message-ID: <873589ro8c.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::42a; envelope-from=zimon.toutoune@gmail.com; helo=mail-wr1-x42a.google.com 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list 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+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-TUID: rqRexmJgj1fe Hi Ludo, On mar., 17 janv. 2023 at 17:09, Ludovic Court=C3=A8s wrote: >> For other cases, such issue is avoided by appending the suffix -next to >> package name; as with ghc-next, python-numpy-next, emacs-next, etc. >> >> Personally, I find the -next trick useful because the package name >> reflects that it is not the default. However, it can be annoying to >> update manifest files when this -next is becoming default. > > To me it=E2=80=99s mostly a packaging issue: I would expect =E2=80=98ocam= l=E2=80=99 to be able > to use =E2=80=98ocaml-ppxlib=E2=80=99. If not, then it should indeed be = =E2=80=98-next=E2=80=99. Currently, yes it is a packaging issue. And yes, the usual trick to fix the issue is to append -next to the package name. As I have tried to explain in bug#60200 [1]. ;-) About this -next, Lars=E2=80=99s answer is, quoting [2]: The -next suffix has the obvious disadvantage that specifications may become invalid as we move -next to the =E2=80=9Cregular=E2=80=9D package. So maybe marking packages =E2=80= =9Cdefault=E2=80=9D like the attached patch does could improve the current situation. Not just for gcc, but also Haskell and Python come to mind. Hence this discussion. :-) The addition of a =E2=80=99properties=E2=80=99 to make the difference betwe= en =E2=80=9Ccurrent=E2=80=9D and =E2=80=9Cnext=E2=80=9D packages appears to be a cleaner fix than to app= end -next to package name. Consider the manifest: (specifications->manifest (list "ghc-next@9.2")) and note that currently the Haskell compiler used by haskell-build-system is ghc@8.10.7. When this default is updated to an higher version of GHC, says version 9.4, then this manifest breaks because ghc-next@9.2 is renamed ghc@9.2; the -next suffix is only applied to version higher than the one used by the Haskell build system. 1: 2: > I=E2=80=99m slightly reluctant because then you can have several packages= that > declare themselves as =E2=80=9Cdefault=E2=80=9D, which looks weird. Reas= oning about why > a given package was chosen would now involve more than version strings. As similarly we can have several packages that declare themselves with the same name and version. :-) If we go for -next, then the two packages gcc-toolchain@{11,12} must be renamed gcc-toolchain-next@{11,12} to be compliant and fixes bug#60200. Why a given package was chosen as =E2=80=9Cdefault=E2=80=9D? Because the p= ackages marked as =E2=80=9Cdefault=E2=80=9D are =E2=80=93 if and only if several ve= rsions are publicly declared =E2=80=93 the ones used by the build-systems and also the ones with many dependents as Numpy. It avoids the -next dance. Well, all in all this =E2=80=9Cdefault=E2=80=9D property appears to me more= elegant than append -next to package name. Cheers, simon