Re: [ELPA] New package: use-package

[Philip Kaludercic]

Payas Relekar <relekarpayas@gmail.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Before this is done, I have a few comments on the current manual.  In
>> the section "Installing from an Elpa Archive", goes into how to
>> configure MELPA/MELPA-Stable.  Is this still necessary?  It might also
>> be a good idea to replace ".emacs" with "init.el", as this is the
>> preferred configuration file AFAIK.  I don't know how important this is,
>> but there are minor typographical issues such as the inconsistent type
>> setting of "use-package" (sometimes with @code, sometimes without), the
>> overuse of @code when @var, @key or @kbd would be better or writing "see
>> @ref" instead of using @xref/@pxref.
>
> Installation instructions should indeed point to GNU ELPA, and I will get to
> fixing that by end of today. I converted the PR to draft to signal it is
> incomplete for now.

Ok.

>> Also, it appears I was mistaken in assuming the manual was finished.
>> There are still large holes:
>>
>> @node Getting Started
>> @chapter Getting Started
>>
>> TODO@. For now, see @code{README.md}.
>>
>> @node Debugging Tools
>> @chapter Debugging Tools
>>
>> TODO
>
> Philip, since we are targeting just ELPA, do you think this can be
> worked on after publishing? Merging to mainline is a distant issue, and
> fixing manual is a future step on that path, as listed before:

Sure, I am not blocking anything, I just wasn't sure if this was a
mistake or not.  If this is the plan, feel free to proceed.  My only
real concern is that I had mistakenly said the documentation on
elpa.gnu.org would be able to replace the contents of the doc/
directory, which isn't the case right now.

>> 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?

>> 4. Add all relevant files to emacs.git
>>    TBD when 3 is done.
>> 5. Ensure everything loads properly



> --