From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id YNpEA60H4GPuMAEAbAwnHQ (envelope-from ) for ; Sun, 05 Feb 2023 20:46:53 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id 4CRJAq0H4GNxNQAAG6o9tA (envelope-from ) for ; Sun, 05 Feb 2023 20:46:53 +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 88FAB2F56B for ; Sun, 5 Feb 2023 20:46:52 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pOkxz-0006WZ-Au; Sun, 05 Feb 2023 14:46:24 -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 1pOkxu-0006V2-RN for guix-devel@gnu.org; Sun, 05 Feb 2023 14:46:19 -0500 Received: from mail-ej1-x642.google.com ([2a00:1450:4864:20::642]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pOkxt-00038v-7F for guix-devel@gnu.org; Sun, 05 Feb 2023 14:46:18 -0500 Received: by mail-ej1-x642.google.com with SMTP id ud5so28776480ejc.4 for ; Sun, 05 Feb 2023 11:46:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; 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=SvV9tqwWw7MgXRP+2GRBdqRXD122TCACiTnWFxR4oKk=; b=GuTwZUHeMNv7v3LbvDf5UG7Zf7NobmvD7Ha+0aix0HzjQNo04icGb7aI1d4qYnIGFb mkNOEIa8ugLgzH/KiRnnyDpf5CuVH0mRlX552hRzWMo700aDnitjSlot1W4+iTi0ZCxY a6zX4pgiopw2Ws9dwF5c5rPocoYcg4X5rb2Gze9Gn11gNg2oFyzYDAdWLaaRiQK6Y48L qTcni7F8a5TtMxSVgHN+h420+6kmMlK/XtPoJ9B5xLg3gMk4v3AcvMyeMMH9kC/zayNJ mJDz9z/TAkOq2EITp8AN8NfQ0Y4qepJhUEFDUfTvWap6Z9qpHfXIFxJpMqqQKKjoX8UB 22gQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=SvV9tqwWw7MgXRP+2GRBdqRXD122TCACiTnWFxR4oKk=; b=56mAGdRx2t2wgraCmwGQYGA7g6dXSMmHLHRaNZd5ySoHlxtq+yzhaAz1DwuHuFpmuM cNDN0ZMRvil8kqDbBKCB3jIlSFkV63R/qutdvnRaL8Q0axrUIY2FvSi5D9XGVKvukHQu /xWfCOwod+t53PgGrliBXr1E82J2v36h9Dgnaiflvay01r/MvZG9BnroSM/0QRbLmkQe uB9p0sAL5P54MxsZoDoYWh4BXvZWcvVQevXb0ImqsyXYf+Dw5rrhc8YJFyTnu40lPsbk Xq+TBR+Z6TTnz+WeVIhy+tScW3wb4bLc5u13FsRNM3hMuPeSbZDcn9kXAUV4dcmojmgz 9MtQ== X-Gm-Message-State: AO0yUKWCcwH9F8aqHUOM7tLDLtgLCbO5G1vAo6g+sUEcymlSJDfOhr4Z g9LsUdFawUBC7/C9iVYImDU= X-Google-Smtp-Source: AK7set+fg+GNO3AVq4BP/IL+qD+MDnSexXnkV5S1Y10wnNhxNhhLwLAhd5nJlMqcL8BeAPSraJLoFg== X-Received: by 2002:a17:906:d961:b0:88c:3502:56d4 with SMTP id rp1-20020a170906d96100b0088c350256d4mr18407663ejb.46.1675626375466; Sun, 05 Feb 2023 11:46:15 -0800 (PST) Received: from lumine.fritz.box (85-127-52-93.dsl.dynamic.surfer.at. [85.127.52.93]) by smtp.gmail.com with ESMTPSA id e11-20020a170906314b00b0084c4b87aa18sm4425721eje.37.2023.02.05.11.46.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 Feb 2023 11:46:14 -0800 (PST) Message-ID: Subject: Re: emacs packaging: do we need to pull existing dependencies ? From: Liliana Marie Prikler To: csantosb@inventati.org Cc: guix-devel@gnu.org Date: Sun, 05 Feb 2023 20:46:13 +0100 In-Reply-To: <87h6w08jeg.fsf@inventati.org> References: <87h6w08jeg.fsf@inventati.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.0 MIME-Version: 1.0 Received-SPF: pass client-ip=2a00:1450:4864:20::642; envelope-from=liliana.prikler@gmail.com; helo=mail-ej1-x642.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 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1675626412; 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: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=SvV9tqwWw7MgXRP+2GRBdqRXD122TCACiTnWFxR4oKk=; b=JFqV9vCkWYUD6mGYNNQJ1jwgjVuTqL8esuUD3FZXh6IM1AR3Y+41DbtU3b5cvozu3IxqNN ZBoBdY5UbkeTeQ0TW8/50U83WC67RqOxMnjOzO/kF2n7h+1iIYDfeJoDPQohecDK9LYbxn nasiNC0ba5rXCkbz1RQFd5xrcEnXx8RDX4fiiknqJrAew+pN5bSAW7x56B2swaA6VZRx7F D0rxqiFVfKxMh2y514+njoRr4ZCDgUKW8Fw+qAagRa2tk4MVyQkVnxDi1Gy+JfIA0VmmJb 2RKCeJrhhsGCWom1KxciHpF4+HZ6MUZvJBs/iE2ERVmDBwys+sFHPFOS+9v59g== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=GuTwZUHe; 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=1675626412; a=rsa-sha256; cv=none; b=UhwjkuaOVK2oOOygLfn4eyW30cMDudYkK7yynULN5dhisyrQYlZFG/dhpOpTmsUp0nbbUv ne+6UCqXNlFkj/LA3BKBCMuFszFTZc2CeVLP+bwQ5cB6VrIjjjVRXschLOPDcq5GoXcaxb TP7QkhBJySM5cReXXsm302e7hZna/cOn3+luuaKzQknU9W/P3p97CnMpJOer2Uz2Ez1QuZ WPfY7iayjyN4Uf7uz5SO1xyXv2DgK43JvZZUbI8YCSUYwhgHrWW/y6MkmW9rucyEmQLdG1 mkcFpaD4FlP6EhlNe+4G3fVc56bzbtgfX7RjiR8vBBenXUJkAGG+RObWmAX6fQ== X-Migadu-Spam-Score: -3.78 X-Spam-Score: -3.78 X-Migadu-Queue-Id: 88FAB2F56B X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=GuTwZUHe; 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 X-TUID: zq2t60WYoKSM Am Sonntag, dem 05.02.2023 um 11:50 +0100 schrieb Cayetano Santos: >=20 >=20 > > > Say for example emacs-org-roam@2.2.2: it requires emacs-org 9.4, > > > which is not specified in the package definition, meaning we > > > always pull the latest available. Do we have to, provided that > > > emacs releases with org? Maybe there is already a clear rule > > > about this topic, but to me this is not clear. We have package > > > definitions with both criteria. >=20 > > I think it's important to think about this in terms of forward > > compatibility.=C2=A0 Is org-roam guaranteed to always work with "the > > current version of Emacs, whatever that may happen to be"?=C2=A0 In tha= t > > case, you could currently drop emacs-org.=C2=A0 If it requires bleeding > > edge symbols on the other hand, or may freely decide that it will > > need them, adding emacs-org to the inputs is a good idea. >=20 > I don=E2=80=99t see your point. This is exactly the responsibility of the > package, declare its dependencies today, regardless of what the > dependencies will be in the future. This is what the =E2=80=99package- > requires=E2=80=99 field is for, including the version number of the > dependencies. Still, there's typically a tendency of things going one way or the other. > If the dependencies of a given package are already there in emacs > (say org-9.2), why do we need to pull org-latest ? If in the future > this changes, an author decides he needs bleeding edge org features, > and changes the version number of org in the =E2=80=99package-requires=E2= =80=99 > field, the new package definition will propagage-require org-latest. > All in all, we may not predict future package needs, pulling > dependencies just in case. >=20 > In any case, and whatever the decission, I think we should clearly > state the way to proceed somewhere, as currently we have a mix of > both. Because people tend to be lazy. If org-whatever used to require bleeding edge org sometime in the past, we won't change it back to the one shipped with emacs because 29.1 is out. If it only ever used the emacs stuff and is backwards-compatible with 25, we might not notice that it even declares the dependency. I gave you both a purist and a pragmatic solution, so you can choose which to follow. I won't press you one way or the other. Cheers