From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Adding use-package to core Date: Sat, 19 Nov 2022 15:36:24 +0000 Message-ID: <87v8nbklc7.fsf@posteo.net> References: <87fsemjs7v.fsf@yahoo.com> <87wn7skqne.fsf@melete.silentflame.com> <83h6yw9hhf.fsf@gnu.org> <87h6ywgfii.fsf@posteo.net> <83edtza04u.fsf@gnu.org> <875yfb5rg5.fsf@posteo.net> <834juv9xpm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9512"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , spwhitton@spwhitton.name, luangruo@yahoo.com, emacs-devel@gnu.org, xenodasein@tutanota.de To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 19 16:37:07 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1owPty-0002I1-6U for ged-emacs-devel@m.gmane-mx.org; Sat, 19 Nov 2022 16:37:06 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owPtX-0007tK-FP; Sat, 19 Nov 2022 10:36:40 -0500 Original-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 1owPtQ-0007t7-7o for emacs-devel@gnu.org; Sat, 19 Nov 2022 10:36:33 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1owPtO-0007WQ-5H for emacs-devel@gnu.org; Sat, 19 Nov 2022 10:36:31 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id B32FB240028 for ; Sat, 19 Nov 2022 16:36:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668872187; bh=p50i0j+kUSZ+va1ZecBoWVkZoU1DG7eD4d0Es0aFP/g=; h=From:To:Cc:Subject:Date:From; b=igbMKgrXYNnf51Asfnsnmm9crqfaIoN/AjBnSdzwloB1DBsrzDyoTxC1BnICSiVkr yNCp3Go/RlLm1GszLeKnH49Jm5kl6E3/V4Ea7KUQWptDunKGLGS+J4SmFgzEOKjBCn exNQrLU+ejXa9OdAoHH4Xm60Vi5fO5K3J/smK6tBVhbbR1lSX04FNY6e8sd70V0g2e n1XpPR5ULH8aAvmiPIgpncowE8c0RVzG8HOIV03J+bJp0soN9utZRAd0nAYp221u71 44UdbykRPn56rDWssb97yjBX4Hpu6pLyEPKGiy+tI4EjTCo89diVC9Eoi1tW85HS6h gjCvrW2r4fldA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NDyRr0TZFz6tnG; Sat, 19 Nov 2022 16:36:24 +0100 (CET) In-Reply-To: (Stefan Monnier's message of "Sat, 19 Nov 2022 10:28:56 -0500") Received-SPF: pass client-ip=185.67.36.65; envelope-from=philipk@posteo.net; helo=mout01.posteo.de 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, 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: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:300186 Archived-At: Stefan Monnier writes: >> packages in a release (which should include the solution for how to >> upgrade such packages after the released Emacs is installed on the >> user's machine), > > FWIW, this has been a solved problem already in Emacs-24: package.el has > always been able to handle the presence of both system-wide packages and > user-installed packages and to pick the most recent version. This is what has been confusing me about Eli's comments. Debian does this all the time, there are a great number of packages that can be installed on a system-wide basis: --8<---------------cut here---------------start------------->8--- $ apt search elpa- WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Sorting... Full Text Search... elpa-a/testing 1.0.0-2 all functions for dealing with associative structures elpa-ac-rtags/testing 2.38-6 all auto-complete back-end for RTags elpa-ace-link/testing 0.5.0-3 all selecting a link to jump to elpa-ace-popup-menu/testing 0.2.1-3 all replace GUI popup menu with something more efficient elpa-ace-window/testing 0.10.0-1 all selecting a window to switch to --8<---------------cut here---------------end--------------->8--- That is also why, in my eyes the issue is reduced to the matter of deciding if the selected ELPA packages are bundled in Git (e.g. as worktrees) or when the tarballs are generated (that distributions use to build their packages). But I am not done with reading through the archives, so I might just be repeating stuff pointlessly.