[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs-29 acd462b0306: ; Improve the use-package manual
From: |
Eli Zaretskii |
Subject: |
Re: emacs-29 acd462b0306: ; Improve the use-package manual |
Date: |
Sun, 11 Dec 2022 09:09:11 +0200 |
> 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.
Re: emacs-29 acd462b0306: ; Improve the use-package manual, Stefan Monnier, 2022/12/10
Re: emacs-29 acd462b0306: ; Improve the use-package manual, Stefan Kangas, 2022/12/10