From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id EH6JBlZa/2TbYgEAauVa8A:P1 (envelope-from ) for ; Mon, 11 Sep 2023 20:20:06 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id EH6JBlZa/2TbYgEAauVa8A (envelope-from ) for ; Mon, 11 Sep 2023 20:20:06 +0200 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 C710E5D644 for ; Mon, 11 Sep 2023 20:20:05 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20221208 header.b=Rh0+pCCs; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1694456406; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:resent-cc: resent-from:resent-sender:resent-message-id:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=883Dx6Ngd/CpMUF4WFlLVMw1lf4a6jROhKdgeXbJV9A=; b=V2oJMfow/i7IUCl+uvI5K/WJ1S24pP2CcKQGzjk5Zww1CzasuNeN3T1AsSpSZMTKLnqPWg z0TfH5ps5gUTkLYEtOGsrO/XCT/CMfUyKkOoGS/Xbzltmc3k/BNTKQrnvtzDQgDGz6zSKR nrjRbi/M3W6UQu+b2eeKkg6/fGgIJzGyXcTu5OU54A5BhyMRT/u1rSKh5+BwppruB95PVa m9h6P782XUNynA1YMKehjVSwG/wexTu3i304Lo0mepYmnkrWoEvow1j1O6SxUBIKrTEDyb +OWVU1hbtK6LF+U/yyubNJmpNyIzIQiQfi0I2oecWo7tSRMZUiYgy4O8R7x/uA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20221208 header.b=Rh0+pCCs; spf=pass (aspmx1.migadu.com: domain of "guix-patches-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-patches-bounces+larch=yhetil.org@gnu.org"; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none) ARC-Seal: i=1; s=key1; d=yhetil.org; t=1694456406; a=rsa-sha256; cv=none; b=FZ/xr+5yO8iZoSwwMhkXVIItlEhmEDdxO8fEERXSsDWX/5sRs88NHwhIwtamYdHipy4ITn MdgCZUHkOYrLZnCPwkV5xIYU8wqtjfqJHSS5VShYQgWVlFRiaBbUxDb+vgbRWC4KLghCcg bRvBXdCWh11j9NPrU7gtvmH5kxNAUC4Tw+KfO5ZzpOcXw29SaRdXT86hIIuA+sBbupLJ9S 37uURLwwhc96k5g6LKIdLTO7s5FVDsWT/+VRds/B3yKZybPx3MDd5YVupB9Am+cg7sOaJJ rqkQpbihf4i/scRy9nzQs5xq+ZL4EqpqyuYd9sR+fwq4bsYhI4pR/p236t3TDA== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qflDX-0005W5-IG; Mon, 11 Sep 2023 14:00:59 -0400 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 1qflDW-0005Vi-GI for guix-patches@gnu.org; Mon, 11 Sep 2023 14:00:58 -0400 Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qflDW-0001gC-8f for guix-patches@gnu.org; Mon, 11 Sep 2023 14:00:58 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qflDa-0003ZY-DJ for guix-patches@gnu.org; Mon, 11 Sep 2023 14:01:02 -0400 X-Loop: help-debbugs@gnu.org Subject: [bug#63088] [PATCH v2] gnu: Add Lc0. Resent-From: Liliana Marie Prikler Original-Sender: "Debbugs-submit" Resent-CC: guix-patches@gnu.org Resent-Date: Mon, 11 Sep 2023 18:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63088 X-GNU-PR-Package: guix-patches X-GNU-PR-Keywords: patch To: zamfofex , iyzsong@envs.net, 63088@debbugs.gnu.org Cc: =?UTF-8?Q?=E5=AE=8B=E6=96=87=E6=AD=A6?= Received: via spool by 63088-submit@debbugs.gnu.org id=B63088.169445522713678 (code B ref 63088); Mon, 11 Sep 2023 18:01:02 +0000 Received: (at 63088) by debbugs.gnu.org; 11 Sep 2023 18:00:27 +0000 Received: from localhost ([127.0.0.1]:54728 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qflD1-0003YY-Cn for submit@debbugs.gnu.org; Mon, 11 Sep 2023 14:00:27 -0400 Received: from mail-ej1-x641.google.com ([2a00:1450:4864:20::641]:53692) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qflCx-0003YK-Lr for 63088@debbugs.gnu.org; Mon, 11 Sep 2023 14:00:25 -0400 Received: by mail-ej1-x641.google.com with SMTP id a640c23a62f3a-99c3d3c3db9so630196966b.3 for <63088@debbugs.gnu.org>; Mon, 11 Sep 2023 11:00:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694455213; x=1695060013; darn=debbugs.gnu.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=883Dx6Ngd/CpMUF4WFlLVMw1lf4a6jROhKdgeXbJV9A=; b=Rh0+pCCstc73c93pT5cFkHKlbm2EyEUtQrSd21VRO4aoxnrPiiT2fz9CeyTAGq83wP cdtxQk88qpA5jl6BmsPCfxl6Ks2LK0MdlLnwkys6onZkZn7gzoMtW8yQejy0u7iS8XKi hbRZNSF9JPZnXlMYmdO8OAy7y0G2HmLpP7klTFTeancnLJvoiv/RjeVb6B3RQDhGr0Ov 7jgRaDfIH39TQTWAOMTNukYnfxURjZ01gBC0rHfB3fyWYeSD9T3PHHv1ALq9I59m7u0o a1XpbaXztnNB6SE/vbmILIZJySlBlTU+Vjd1dsTP86d/UGQWzmhwLTcABIvi+2Gs5dwO zcFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694455213; x=1695060013; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=883Dx6Ngd/CpMUF4WFlLVMw1lf4a6jROhKdgeXbJV9A=; b=DvL+GpvBrFCHErx/+7emXiJ7hDmzBi5PBnpe2zCcRrSLe1zOE21L9wUNLs8S2oOJAe NIxUqdgE6qe37W1uHrNlsipcVNXe55vnAM3HaiT3q7oSTnSZgpCdxzgMuTwHW9I4+kaX tg2DYBRvgdyL0v17/xQundLoJv68fq6HO1L5T+5i+w0MsZl9F1o4HJJoeoPJ8XktzPaM BAxKYRlbUxjAQMLW4pOgZKSGwgHKET2CQ+ISBDilOVACusp9ipyQXOyWWvUXsbTEuL1E 0Eo93KcSp3KXOuYGDX/yT2hanE1H7C2exFz260XnxBIh37t9Z/fUcrT9hjZa8HWTZ4KX oTyA== X-Gm-Message-State: AOJu0YyEd//85c7Q2dUDbcdE5dEtLCJ74JZLCi3B1IaXuzsuj7I1DHS5 nRIYQbJYK1hNt8dqoxwff+0= X-Google-Smtp-Source: AGHT+IEXzMA7g4eBQZ4iHuQSCzRLmJ9+z6p508IgPUvFXFAStrnyMxVtVYX8/yrrHx8hFS2qNSYxPQ== X-Received: by 2002:a17:906:3057:b0:99d:ddae:f5d4 with SMTP id d23-20020a170906305700b0099dddaef5d4mr7944799ejd.44.1694455213004; Mon, 11 Sep 2023 11:00:13 -0700 (PDT) Received: from lumine.fritz.box (85-127-52-93.dsl.dynamic.surfer.at. [85.127.52.93]) by smtp.gmail.com with ESMTPSA id ck8-20020a170906c44800b009a5f1d1564dsm5658747ejb.126.2023.09.11.11.00.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Sep 2023 11:00:11 -0700 (PDT) Message-ID: <90ea3981901d0b274e673ebf72c6755a07a1ce1b.camel@gmail.com> From: Liliana Marie Prikler Date: Mon, 11 Sep 2023 20:00:10 +0200 In-Reply-To: <973443928.2024365.1694427755815@privateemail.com> References: <3cc41c81a301fb53c564508d3cbcf92270695d1b.1694082083.git.iyzsong@member.fsf.org> <973443928.2024365.1694427755815@privateemail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4 MIME-Version: 1.0 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: guix-patches@gnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+larch=yhetil.org@gnu.org Sender: guix-patches-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx1.migadu.com X-Migadu-Spam-Score: -5.12 X-Spam-Score: -5.12 X-Migadu-Queue-Id: C710E5D644 X-TUID: riITvlJKDXVw Am Montag, dem 11.09.2023 um 07:22 -0300 schrieb zamfofex: > > recursive? #t is meh ._. > > Can we work around that? >=20 > Yes, presumably easily, but I don=E2=80=99t think it would be a good idea= in > this case, because it isn=E2=80=99t used to build bundled software, but > rather just for a small project=E2=80=90specific pair of source files (th= at > are in a separate repo just because they are used by other repos of > the project too). In that case, a comment explaining this in 1-2 lines would probably be fine. > > Can we use search-input-file or the like here? >=20 > Probably. Though would it be reasonable to package the network > separately instead? Note that Lc0 is able to load various networks, > and there is no canonical network, so maybe it would be useful to > have it in a different package so that more can be potentially added > in the future. >=20 > Then people could use them with something like =E2=80=98guix shell lc0 lc= 0- > NETWORK_NAME=E2=80=99. Sounds reasonable to me. Do add a phrase or two about this to the lc0 description though if it doesn't even ship a basic network. >=20 > > Is Lc0 =3D Leela Chess Zero?=C2=A0 What's the connection? >=20 > =E2=80=9CLc0=E2=80=9D, =E2=80=9CLeela Chess Zero=E2=80=9D, =E2=80=9CLCZer= o=E2=80=9D, and sometimes just =E2=80=9CLeela Chess=E2=80=9D > can be used roughly interchangeably to refer to the project as a > whole. Though, occasionally, people will use the term =E2=80=9CLc0=E2=80= =9D > (sometimes capitalised as =E2=80=9Clc0=E2=80=9D) to refer specifically to= the =E2=80=98lc0=E2=80=99 > executable, which can use the networks from the Leela Chess Zero > project, but networks created by other people too, including those of > e.g. the Maia project, see and > >=20 > At some point (very early on), the code for the executable was > rewritten or otherwise largely refactored, and at the same time > renamed from =E2=80=98lczero=E2=80=99 to the current =E2=80=98lc0=E2=80= =99, so sometimes (very rarely > nowadays), people will use the term =E2=80=9Clc0=E2=80=9D (or =E2=80=9CLc= 0=E2=80=9D) to refer > specifically to this new executable and code base, contrasting with > the former =E2=80=98lczero=E2=80=99 executable and its code base. >=20 > Honestly, this all feels convoluted to me, so I usually like to use > the terms interchangeably, and I don=E2=80=99t think using them different= ly > in the package description is a good choice. In that case, for the description we should probably go with "Leela Chess Zero" or "@acronym{lc0, Leela Chess Zero}" Cheers