From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id eAm7Inm6KmWeOwEA9RJhRA:P1 (envelope-from ) for ; Sat, 14 Oct 2023 17:57:45 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id eAm7Inm6KmWeOwEA9RJhRA (envelope-from ) for ; Sat, 14 Oct 2023 17:57:45 +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 3C39534530 for ; Sat, 14 Oct 2023 17:57:45 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=V3T2EKZp; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1697299065; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=auEJiFW8iTH/mnt7wf8w94U9n0uQQDFom3Ty/rH1crQ=; b=kx8pyqVZzl/r/TYzwqh0IVDlUwnYwDv/7xCoBxIHdlXfA+RYeytIH710yknHqhWLQvHg5l EqDqmQanwmEDpkJcGTtZx93mc0h0A7L6idViHEmEI+ks8VatYOH7j6huDXOyBmzRDo0fO8 RBWJAVxh2nfZJFzUfy35/p7eMfRY5nZemtP+FyP08nI0bm6pacOYNwFx7+Yt8nZUnNPyEh upW/ucovbLY5VmgFxMdjKapA1dwROFDUb5FLroWfnwUOGzi7ver/jUkyt9uW4VNAmCQqk8 NT0RkCoutShrtpQsBpBI9ER6is4U4rduXjNlPzIicjpf4uT+HjFRCLtJWiBqQQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=V3T2EKZp; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1697299065; a=rsa-sha256; cv=none; b=ZajlbSw9rkNpOXrcyfsb+8DZ1Z7qj3CR8XIILZWuQ8sQjOZiNms4epL7jvbhyAlTr9tZkg v2TX2bpybRNXpDmI7HtuCtAUa+Olpx6B0Q9T278p+aprCfZIC5jyT/Or3Av29+AaVvD9GP EuCBFLRI/H3p720q/3OLuhli/jJrM4OfyYrqpzycm8W5CQ4XpThuw7b5AS2FNDKmsjivqi w2akvRpRV2pZ3fxHNJdSoQScB+ZsM3e13nskwUZBDEVPeINs7fiaoZQGiIpFuIVCb3Bh6u qtwZ4v5SNt/bZkMa3NXlzXenTYXEtyhm4KaYYTJ9S1103RIfGxX0p/NxRmKBkQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qrh0y-0002UJ-1t; Sat, 14 Oct 2023 11:57:20 -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 1qrh0w-0002U7-Ik for guix-devel@gnu.org; Sat, 14 Oct 2023 11:57:18 -0400 Received: from mail-qt1-x82c.google.com ([2607:f8b0:4864:20::82c]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qrh0u-0000aF-Us for guix-devel@gnu.org; Sat, 14 Oct 2023 11:57:18 -0400 Received: by mail-qt1-x82c.google.com with SMTP id d75a77b69052e-41b1a3329f2so20641931cf.0 for ; Sat, 14 Oct 2023 08:57:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697299035; x=1697903835; darn=gnu.org; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=auEJiFW8iTH/mnt7wf8w94U9n0uQQDFom3Ty/rH1crQ=; b=V3T2EKZpYDIb7YkNY+YMQKht3XQYCFcS/pGf60OuMFbQmbHr5jIo8sDK60jTeBUGq+ gowKOHHfTvMkcCs5iWQPIOnBMbUZhUoQ7seEAL3XA5XhxtS+6f8Y+yeWj4bxdC2xUzSm Q2tLBI4mZZRlKEvh8TQDlcQ9NOYSSSkG2z4jzTDlPWde9h7Z5Z22daGwRQHw31JAcD3K 2FuUV9Opn2dibDzglduI+JzNSKqBj5uhO47j/aQwy+aIwIV0r+n1XizS+t4X5oG8Nsnv maEcgTmAn+czOrvwu1A/j3U3E2Z1YqjJ4fa7MSGYyzEjGeW+4ZrZHdkqdm4oyhpj5kuk Zo/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697299036; x=1697903836; h=mime-version:user-agent: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=auEJiFW8iTH/mnt7wf8w94U9n0uQQDFom3Ty/rH1crQ=; b=id7+gyCuVMmP+Ag2Cs0sgrIolq3Mzj4lLaM0SBfBN9AWQsQ2JLJfQRNy7pLI6UTVgm 0OS46jZk7LwN5fLlPc8r8mPN/hVEvhTJZxnawMedoBk9EE0J+D7xBnufJM4bbfGtA1Ts 4uPwYEipaR0g6LHS7j4PT+qDGLJsi5VPe7a5++o+Ioq0Ncjko3JUCAHLKBH6jE2WwQ+U kGz15xXNTtXPxkHq15WHhGNrcZaJuy2ZFXeb0beQsNs+mHSyenIGgObEHINOpVZEC9kF INKGvspj/Xye8itKN6nVldO3Mx6vASuwSBLQGxBVWGPz16aRBK1pfJR10o8VIEZGCKEz PftA== X-Gm-Message-State: AOJu0Yz4dr2X3GazL3uDuiIwaqN6PJ98s7Q7VBf0mL2hZDSMwA5oUrm4 dhTbcyyGT3ItAFJniJRqNNU= X-Google-Smtp-Source: AGHT+IEgXOIlOgfTBkGvUDjcDWJ/8ljXSXg9oTIFrLSAPzAD5/tX5W9YRzIZCiBcfBM+lPnCHMcSGA== X-Received: by 2002:a05:622a:211:b0:418:af4c:1853 with SMTP id b17-20020a05622a021100b00418af4c1853mr33049687qtx.25.1697299035687; Sat, 14 Oct 2023 08:57:15 -0700 (PDT) Received: from hurd (dsl-156-181.b2b2c.ca. [66.158.156.181]) by smtp.gmail.com with ESMTPSA id l18-20020ac84592000000b0041b0b869511sm1570565qtn.65.2023.10.14.08.57.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 14 Oct 2023 08:57:15 -0700 (PDT) From: Maxim Cournoyer To: Ekaitz Zarraga Cc: "guix-devel\@gnu.org" , Fredrik Salomonsson Subject: Re: Fw: Question regarding qmk firmware In-Reply-To: (Ekaitz Zarraga's message of "Sun, 08 Oct 2023 10:34:10 +0000") References: <87r0m6xh3c.fsf@posteo.net> Date: Sat, 14 Oct 2023 11:57:14 -0400 Message-ID: <87h6mt2o4l.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::82c; envelope-from=maxim.cournoyer@gmail.com; helo=mail-qt1-x82c.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-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -9.46 X-Spam-Score: -9.46 X-Migadu-Queue-Id: 3C39534530 X-Migadu-Scanner: mx2.migadu.com X-TUID: kBuJT0PV2dqt Hi Ekaitz, Ekaitz Zarraga writes: > Hi > > I want to forward this message to guix-devel because it is a clear > case of some (actually good) technical decision affecting users in > unexpected ways. > > Now, after the change, a user might run `guix search avr-toolchain` and find nothing. Same for ARM. > > This is a shame, because we have toolchains for those architectures > but converting them to a function that returns the package leave many > users that are not used to read guix's code thinking those packages > are gone. > > Maybe we should create some kind of fake packages that show up in > `guix show` and `guix search` that have a short tutorial on how to use > packages that come from a function like these. > This way providing the same interface for every package regardless where they are coming from. > > I leave it as food for thought. There's this series: https://issues.guix.gnu.org/66263 that proposes to still have a module which would include the cross-toolchain as packages again; it'd be in a new module, and as I pointed to in my review we'd need to stress hard that this module is only for convenience and shouldn't be imported anywhere else in the Guix source code (which seems a bit of a slippery slope to me, as people rarely read the module commentary, and rightly assume that any package present in Guix can be used as another package's input). We can't deprecate the package I think, as the replacement is not of the same type (it's replaced by a procedure). A NEWS could perhaps have helped, though it's not as good as a deprecation. -- Thanks, Maxim