From: No Wayman <iarchivedmywholelife@gmail.com>
To: 69410@debbugs.gnu.org
Subject: bug#69410: 30.0.50; [WISHLIST] Use-package: allow :ensure to accept package spec instead of separate :vc keyword
Date: Mon, 01 Jul 2024 10:28:50 -0400 [thread overview]
Message-ID: <87v81p5gpp.fsf@gmail.com> (raw)
In-Reply-To: <87wmqryzv2.fsf@gmail.com>
-------------------- Start of forwarded message
--------------------
From: No Wayman <iarchivedmywholelife@gmail.com>
To: Tony Zorman <soliditsallgood@mailbox.org>
Subject: Re: bug#69410: 30.0.50; [WISHLIST] Use-package: allow
:ensure to
accept package spec instead of separate :vc keyword
Date: Mon, 01 Jul 2024 10:06:44 -0400
Tony Zorman <soliditsallgood@mailbox.org> writes:
> Thanks. To be honest, I'm not a big fan of trying to cram
> everything
> into :ensure.
I wouldn't describe it as "cramming everything into :ensure".
:ensure could accept:
- nil: do not attempt to install anything
- t: attempt to install via the user's chosen default package
manager
- a symbol name: install package matching that symbol name with
default package manager
- a recipe spec: install via a forge capable package manager using
that package recipe.
It's not that complicated.
If anything, it would encourage package-manager authors to support
a basic subset of keywords for the package recipe spec, increasing
cross-compatibility for package recipes.
> By the same thought, one might
> argue that something like :load-path should be inlined into
> :ensure as
> well, which is not a good idea in my opinion.
No one is arguing that.
> In either case, I think that
>
> (use-package example
> :ensure (:url "https://www.forge.com/maintainer/example"))
>
> is not that much more verbose (or harder to adjust) than
>
> (use-package example
> :ensure t
> :vc (:url "https://www.forge.com/maintainer/example"))
This is not what package authors provide in practice.
Taking your example, the package installation section of a
package's README would look something like this:
> (use-package example
> :ensure t
> ;; uncomment one of the following for your package manager
> of choice...
> :vc (:url "https://www.forge.com/maintainer/example")
> :straight (:repo "https://www.forge.com/maintainer/example")
> :elpaca (:url "https://www.forge.com/maintainer/example")
> :some-other-package-manager (:url ...)
> ;; and so on...
> )
Using my proposal:
> (use-package example
> :ensure (:url "https://www.forge.com/maintainer/example"))
If a package manager decides not to support the :url recipe
keyword, that's on them.
> This is especially true since use-package-always-ensure exists
> (and many
> people use it) so one would just have to write
It's not about the `:ensure t`, it's about every package manager
requiring their own, separate interface to use-package, when they
basically operate on the same data structure.
> Any kind of backwards compatibility with a hypothetical
> :straight
> keyword would not work in either case, because :straight already
> exists
> in straight.el and it has a completely different package
> specification
> attached to it.
Not asking for this, either.
I'd like to see the `:straight` keyword go away.
Making that happen would be the burden of straight's maintainers
(of which I am one).
>> My own take is that setting aside timing issues and the fact
>> that the
>> Emacs 30 branch has been cut, ...
I brought it up well before then, but nobody was interested/aware
enough to reply.
(Not the first time it's happened on these mailing lists, and a
primary reason I seldom chime in.)
>> - The :vc keyword allows just passing t to download the package
>> as
>> specified in the ELPA archive. I don't see an elegant away
>> to allow
>> this using :ensure.
>
> Yes backwards compatibility might be a bit of a pain—especially
> with a
> view on use-package-always-ensure—save having self-defeating
> constructs
> like :ensure (:vc …).
It's evident there's little enthusiasm for the idea now, too.
That being the case, I'll relax the constraints on Elpaca's recipe
format I placed in hopes of offering an easier switch between
package managers for users.
Thanks for the input.
-------------------- End of forwarded message --------------------
next prev parent reply other threads:[~2024-07-01 14:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 16:06 bug#69410: 30.0.50; [WISHLIST] Use-package: allow :ensure to accept package spec instead of separate :vc keyword No Wayman
2024-06-30 10:42 ` Philip Kaludercic
2024-07-01 13:37 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-01 19:57 ` Philip Kaludercic
2024-07-03 19:56 ` Tony Zorman via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87zfr15hqj.fsf@gmail.com>
2024-07-01 14:28 ` No Wayman [this message]
2024-07-03 20:34 ` Philip Kaludercic
2024-07-08 12:12 ` No Wayman
2024-07-08 15:52 ` Philip Kaludercic
2024-07-09 2:30 ` No Wayman
2024-07-09 9:02 ` Philip Kaludercic
2024-07-09 9:56 ` No Wayman
2024-07-09 7:34 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-09 8:26 ` Philip Kaludercic
2024-07-03 19:51 ` 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=87v81p5gpp.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=69410@debbugs.gnu.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).