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 11:02:28 +0000 Message-ID: <87k03r437f.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> <871qpz5k7y.fsf@posteo.net> <83r0xz8cd6.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="33809"; mail-complaints-to="usenet@ciao.gmane.io" Cc: spwhitton@spwhitton.name, luangruo@yahoo.com, emacs-devel@gnu.org, xenodasein@tutanota.de To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 19 12:02:50 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 1owLcX-0008WD-Ly for ged-emacs-devel@m.gmane-mx.org; Sat, 19 Nov 2022 12:02:49 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owLcL-0000qu-2q; Sat, 19 Nov 2022 06:02:37 -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 1owLcH-0000qO-Ql for emacs-devel@gnu.org; Sat, 19 Nov 2022 06:02:33 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1owLcF-0006Ct-4c for emacs-devel@gnu.org; Sat, 19 Nov 2022 06:02:33 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id DD9B9240103 for ; Sat, 19 Nov 2022 12:02:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1668855748; bh=z9YXBAKDJSkBB6GAF9u8ViXeKr2l7cy0RrTedsQvuYI=; h=From:To:Cc:Subject:Date:From; b=lTl+Kn9AWYL98qBZA2vx/qVU0nkyCzvraoSlVPSXVJeFQ2KJMxcvJxhpxY1d4FDUQ xZEmiDruXskGtJ8oUKwimddMNqJdNZQFd/HdvVFFaRkGaCYyBuvt96q1wf9sVqo4s5 FNzrj9ZHW3eU7IWSVsEdp42g6vxbRomLtIcVsKunY6z5EfNRcaCLtG/9I3YmPzv4c8 f0Z6tIOnvfN3Myf3YMjMre4J61fqESrbXcZ+Jo5iR5J0eKifZVBOt+h5X5cn83erKF og9au0siey9COW/gJ/7mXbtlBvObqelGc0CI78abYxzKla/7Bj1aIw2pINi/LzzAqW /UtLaZpP2QDlg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4NDrMm1r5Bz9rxN; Sat, 19 Nov 2022 12:02:28 +0100 (CET) In-Reply-To: <83r0xz8cd6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Nov 2022 12:31:01 +0200") Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.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, RCVD_IN_MSPIKE_H2=-0.001, 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:300152 Archived-At: Eli Zaretskii writes: >> From: Philip Kaludercic >> Cc: spwhitton@spwhitton.name, luangruo@yahoo.com, emacs-devel@gnu.org, >> xenodasein@tutanota.de >> Date: Sat, 19 Nov 2022 10:09:37 +0000 >> >> Eli Zaretskii writes: >> >> >> 2. Are we talking about GNU ELPA or both NonGNU ELPA and GNU ELPA. >> > >> > GNU ELPA only. >> >> OK, but then again, what to do about Magit being on NonGNU ELPA. > > AFAIU, an effort to collect all the assignments for Magit is under > way, with the purpose of adding Magit to ELPA and/or Emacs. That I did not know, but I can't find anything on the topic online either. >> > We could do that, but until we have a reliable way of including ELPA >> > 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), doing these secondary jobs is IMO just a waste of >> > time and energy. For example, if the solutions are far away in the >> > future, the list of contenders you collect now will be outdated by >> > then, and will need to be redone anew. >> > >> > The issues we are touching here were all discussed in the past, and >> > the difficulties that need to be resolved were described and also >> > discussed. It's nothing new, and I don't think anything's changed >> > since those discussions, we are still where we were back then wrt our >> > ability to include ELPA packages. >> >> What exactly is the complication here? Wouldn't it be possible to have >> a "contrib"/"elpa"/... directory under lisp with ELPA packages that are >> prepared before packaging? Or should these packages be moved into the >> core? Would using fancy tricks like git worktrees, as done by >> elpa-admin be a possible approach to tackle the issue? > > The basic issue is: when I install a new Emacs version, and later want > to upgrade to a newer version of a package maintained on ELPA, how > does Emacs do that, and what are user-level implications, given the > existing methods of installing Emacs, both by building it locally and > installing a distro? Ok, I get that. > Again, the details of this were described and discussed, so I suggest > to look up those past discussions and read there. I'll try that too. Do you have any specific discussions in mind. Searching the archive can be a bit difficult when looking for general discussions.