From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org, johnw@newartisans.com
Subject: Re: emacs-29 acd462b0306: ; Improve the use-package manual
Date: Sun, 11 Dec 2022 09:09:11 +0200 [thread overview]
Message-ID: <83o7sav2lk.fsf@gnu.org> (raw)
In-Reply-To: <jwvh6y3ndhd.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 10 Dec 2022 17:01:13 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>, John Wiegley
> <johnw@newartisans.com>
> Date: Sat, 10 Dec 2022 17:01:13 -0500
>
> >> I think this part of `use-package` is a result of its having been
> >> designed before things like `package.el` became common practice (the
> >> main effect of which (in this respect) has been to make `;;;###autoload`
> >> cookies usable in all packages without any extra work on the package's
> >> author's side).
> >
> > Agreed. Another thing is that `use-package' also tries hard to be
> > package manager agnostic, and that also shows in places. I wonder if
> > that's somehow also connected to the above.
>
> Im not sufficiently familiar with all the package managers out there,
> but my impression is that it shouldn't make much difference in
> this respect.
But please don't ignore the use case of someone installing packages
manually, or from places that don't support package.el's methods. It
could be just a bunch of Lisp under site-lisp. For example, some
programs come with Emacs interface packages that they install under
site-lisp; examples include ID Utils, Guile, etc.
IOW, package.el doesn't solve all the aspects of managing unbundled
Lisp libraries for Emacs.
prev parent reply other threads:[~2022-12-11 7:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167059642832.4265.15913417645926264658@vcs2.savannah.gnu.org>
[not found] ` <20221209143348.961DEC0E4CA@vcs2.savannah.gnu.org>
2022-12-10 11:57 ` emacs-29 acd462b0306: ; Improve the use-package manual Stefan Kangas
2022-12-10 14:26 ` Eli Zaretskii
2022-12-10 20:34 ` Stefan Kangas
2022-12-11 6:22 ` Eli Zaretskii
2022-12-11 14:24 ` Stefan Monnier
2022-12-11 20:04 ` John Yates
2022-12-12 1:35 ` Stefan Kangas
2022-12-12 1:34 ` Stefan Kangas
2022-12-10 16:20 ` Stefan Monnier
2022-12-10 16:30 ` Philip Kaludercic
2022-12-10 16:40 ` Stefan Monnier
2022-12-12 19:37 ` John Wiegley
2022-12-12 20:06 ` Philip Kaludercic
2022-12-10 20:33 ` Stefan Kangas
2022-12-10 22:01 ` Stefan Monnier
2022-12-11 7:09 ` Eli Zaretskii [this message]
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=83o7sav2lk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=johnw@newartisans.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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).