From: Philip Kaludercic <philipk@posteo.net>
To: Tony Zorman <soliditsallgood@mailbox.org>
Cc: 67955@debbugs.gnu.org
Subject: bug#67955: [PATCH] Add use-package-vc-prefer-newest user option
Date: Mon, 15 Jan 2024 07:09:02 +0000 [thread overview]
Message-ID: <87fryzxecx.fsf@posteo.net> (raw)
In-Reply-To: <878r4t18in.fsf@hyperspace> (Tony Zorman's message of "Sat, 13 Jan 2024 17:51:44 +0100")
Tony Zorman <soliditsallgood@mailbox.org> writes:
> On Fri, Jan 12 2024 16:32, Philip Kaludercic wrote:
>> Tony Zorman <soliditsallgood@mailbox.org> writes:
>>> ++++
>>> +*** New user option 'use-package-vc-prefer-newest'.
>>> +This allows the user to always install the newest commit of a package
>>> +when using the ':vc' keyword.
>>
>> I wonder if this should be merged into the previous point, or if it is
>> even worth mentioning, since it is part of a few feature that has been
>> added in Emacs 30.
>
> No strong opinions here, I can change this to whatever people prefer.
Let us leave it then, because I don't know what would be better either.
>>> +(defcustom use-package-vc-prefer-newest nil
>>> + "Prefer the newest commit over the latest release.
>>> +If non-nil, the `:vc' keyword will prefer the latest commit of a
>>> +package instead of the latest stable release. This has the same
>>> +effect as specifying `:rev :newest' in every invocation of `:vc'."
>>> + :type 'boolean
>>> + :version "30.1"
>>> + :group 'use-package)
>>
>> I would briefly mention what the issue could be when setting this option
>> to non-nil, just to give some context as to why it is disabled by default.
>
> Do you mean something like how this goes against what [Non]GNU ELPA do,
> and could lead to increased instability (as we are, by definition,
> tracking a moving target)? I guess a lot of users will be familiar with
> this style of development from MELPA, so I'm not sure any additional
> warning here is necessary. Again, I don't feel very strongly about this,
> so if you want this changed I'll think of something.
Yes, that was what I meant. I don't want to assume that users are
familiar with MELPA, so a brief comment to that effect should suffice.
Thanks!
next prev parent reply other threads:[~2024-01-15 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 18:13 bug#67955: [PATCH] Add use-package-vc-prefer-newest user option Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 21:01 ` Stefan Kangas
2024-01-12 16:32 ` Philip Kaludercic
2024-01-13 16:51 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 7:09 ` Philip Kaludercic [this message]
2024-01-15 20:16 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 7:33 ` Philip Kaludercic
2024-03-30 8:15 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-30 13:42 ` Philip Kaludercic
2024-03-30 14:27 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87fryzxecx.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=67955@debbugs.gnu.org \
--cc=soliditsallgood@mailbox.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).