unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mark A. Hershberger" <mah@everybody.org>, 75328@debbugs.gnu.org
Subject: bug#75328: 31.0.50; use-package cannot override a built in package
Date: Sat, 04 Jan 2025 21:57:18 +0000	[thread overview]
Message-ID: <874j2ensxt.fsf@posteo.net> (raw)
In-Reply-To: <86sepybfsx.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 04 Jan 2025 20:21:50 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "Mark A. Hershberger" <mah@everybody.org>
>> Cc: 75328@debbugs.gnu.org
>> Date: Sat, 04 Jan 2025 10:50:21 -0500
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Did you try customizing package-install-upgrade-built-in?
>> 
>> Yes.  I also reported this to Jonas[1] and in the following discussion
>> he suggested that and I tried it[2].
>> 
>> The following does not check out the transient repository into
>> ~/.emacs.d/elpa/:
>> 
>>     rm -rf ~/.emacs.d &&
>>     echo '(setq package-install-upgrade-built-in t)
>>     (use-package transient :vc (:url "https://github.com/magit/transient" :rev :newest) :ensure t)' > ~/.emacs &&
>>     ~/bin/emacs
>
> Philip, shouldn't package-install-upgrade-built-in allow upgrading a
> built-in package via use--package's :vc keyword?

Built-in packages are not supported by package-vc right now, as
emacs.git is not a emacs package the way ELPA intends it.  There is also
the annoyance that without custom code (which would be doable if we had
to) we would have a separate checkout of emacs.git for every built-in
package that one wishes to clone that way.  This would be a lot easier
if Git would support subtree or single-file checkouts...





  reply	other threads:[~2025-01-04 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03 22:29 bug#75328: 31.0.50; use-package cannot override a built in package Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04  7:24 ` Eli Zaretskii
2025-01-04 15:50   ` Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 18:21     ` Eli Zaretskii
2025-01-04 21:57       ` Philip Kaludercic [this message]
2025-01-05  6:36         ` Eli Zaretskii
2025-01-05 20:33           ` Philip Kaludercic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874j2ensxt.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=75328@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mah@everybody.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).