From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#71356: use-package doesn't load org from elpa Date: Mon, 10 Jun 2024 15:18:21 +0300 Message-ID: <86y17d7zzm.fsf@gnu.org> References: <86plsvk57o.fsf@gnu.org> <86ed9aip6z.fsf@gnu.org> <87ed9abnqn.fsf@posteo.net> <868qziifzd.fsf@gnu.org> <87msnt1gkf.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26688"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 71356@debbugs.gnu.org, philipk@posteo.net, paaguti@gmail.com To: Andrea Corallo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jun 10 17:13:13 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1sGght-0006jK-0d for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 10 Jun 2024 17:13:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sGghU-0000Da-9A; Mon, 10 Jun 2024 11:12:48 -0400 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 1sGghS-0000C8-1p for bug-gnu-emacs@gnu.org; Mon, 10 Jun 2024 11:12:46 -0400 Original-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 1sGghR-0007Wx-Ow for bug-gnu-emacs@gnu.org; Mon, 10 Jun 2024 11:12:45 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sGghi-0003e8-DD for bug-gnu-emacs@gnu.org; Mon, 10 Jun 2024 11:13:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 10 Jun 2024 15:13:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71356 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 71356-submit@debbugs.gnu.org id=B71356.171803234013886 (code B ref 71356); Mon, 10 Jun 2024 15:13:02 +0000 Original-Received: (at 71356) by debbugs.gnu.org; 10 Jun 2024 15:12:20 +0000 Original-Received: from localhost ([127.0.0.1]:40744 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sGgh2-0003bo-5o for submit@debbugs.gnu.org; Mon, 10 Jun 2024 11:12:20 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47768) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sGggv-0003Zs-OL for 71356@debbugs.gnu.org; Mon, 10 Jun 2024 11:12:14 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sGdyh-00059P-Mv; Mon, 10 Jun 2024 08:18:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Y/oGpf349uCtCTfzezcTHcqhT3FX5R2xIrBslAiiLIg=; b=AIp6yxG4fM6E CZ4OKnGMyFyIc7+3KqEn4vf3ZvSyxnpfQAXUlIX83S8xlbz4BMZPTbrWOCVNypULQJidyREQ5Jnod LjJAEeeY1rwj4vsoF4GJxX3GEGGpab7qr0cl3eaNYLWPv4TfxxgvdugSF3Sdhwrn5PB+q3QBrFnv0 CKpX9QW+SMK3IxSnaTooZzy/hlPDg3+xjdLeiqBM/Kbj3NPs7WxMgG7a1/lzn+tGVzaGrFSGDFw1s siGBKsoQ74mLCJHeXFwb3ammvanzEN75YBWoboL58bUZSUXEYunaX5mR53cPk/hQvC/+fSkRw/jez kGbhCLx/dDkg5gzuTEv2pA==; In-Reply-To: (message from Andrea Corallo on Mon, 10 Jun 2024 04:17:21 -0400) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:287037 Archived-At: > From: Andrea Corallo > Cc: Eli Zaretskii , paaguti@gmail.com, 71356@debbugs.gnu.org > Date: Mon, 10 Jun 2024 04:17:21 -0400 > > Philip Kaludercic writes: > > > Eli Zaretskii writes: > > > >>> From: Philip Kaludercic > >>> Cc: Pedro Andres Aranda Gutierrez , acorallo@gnu.org, > >>> 71356@debbugs.gnu.org > >>> Date: Thu, 06 Jun 2024 06:15:44 +0000 > >>> > >>> Sorry for the delayed response; I don't think that has to be expected. > >>> While use-package can utilise package.el for package management, my > >>> impression is that it is at liberty to be more flexible/declarative. > >> > >> Doesn't use-package utilize package.el already? > >> > >> If not, how does it handle installation and upgrades? by its own code? > > > > By default it uses package.el, but there is an option to change it. > > > >>> > Do you have package-install-upgrade-built-in set non-nil? If not, can > >>> > you set it non-nil and try the recipe again? > >>> > >>> I have tried it out myself, and it doesn't appear to do anything. The > >>> issue looks like that `package-installed-p' doesn't respect > >>> package-install-upgrade-built-in or :pin. > >> > >> We should fix that, I think. If package-install-upgrade-built-in is > >> non-nil, use-package should upgrade built-in packages. > >> > >>> > As for a feature request: what exactly is the feature requested here? > >>> > Are you saying that use-package should automatically upgrade built-in > >>> > packages? If so, I don't think this will fly, since it would mean > >>> > inconsistencies with package-install. > >>> > >>> IIUC the feature would be that if a use-package form has a > >>> > >>> :pin gnu > >>> > >>> argument, then this is an indication that we want to install the package > >>> from GNU ELPA, disregarding the fact that Emacs already has a built-in > >>> version of the same package. Sort of a package-local version of > >>> `package-install-upgrade-built-in'. > >> > >> I'm not sure. People tend to copy/paste recipes from the Internet > >> without really understanding what they do. I think a simple :pin > >> should not be sufficient, we need some specialized keyword (in > >> addition to supporting package-install-upgrade-built-in). > > > > To me :pin would make perfect sense, as it explicitly expresses what > > archive we want to follow for package upgrades. > > +1, also use-package interface is very declarative and I'm not sure > having it influenced by a dynamic var would match user expected > behavior. If you prefer, we could add a new :foo keyword to mean this. But unconditionally changing what :pin means in these cases is out of the question.