A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00700.html below:

Adding use-package to core

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Stefan Kangas Subject: Adding use-package to core Date: Fri, 11 Nov 2022 21:42:26 -0800
Payas Relekar <relekarpayas@gmail.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>>>> 1. Get use-package in ELPA
>>>> 2. Complete all documentation
>>>> 3. Prepare documentation in texinfo
>>>>    Will cross that bridge when 2 is done.
>>
>> While we are at it, is there a rationale for this order?  I mean, there
>> is no hurry, right? My misunderstanding was that the order was 2 -> 3 ->
>> 1.  Or are you planning to have use-package ready for Emacs 29?
>
> If you mean merging use-package into emacs.git, that will definitely not
> be happening (at least if I'm the only one working on it).
[...]
> From my understanding, ELPA has less stringent requirements for
> documentation and testing compared to core. Since I cannot commit enough
> time to complete all the tasks before expected 29 branch-off, ELPA is a
> good compromise IMO.

OK, I'll bite.  I have time to dedicate to this task; perhaps we can
move quickly enough for Emacs 29.  Ultimately, the decision will be with
the maintainers, but it seems to me that use-package.el itself is in
shape for inclusion.

Could you write up a summary of what needs doing before we can add
use-package to emacs.git?  Is it just a matter of writing up some more
documentation, or is there more that needs doing?

> As for the order rationale, getting use-package to ELPA means less
> friction and more users can try it out, more feedback, more eyeballs,
> basically.

If we get it into core, we can make it into a :core package.



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4