From: Jonas Bernoulli <jonas@bernoul.li>
To: 62524@debbugs.gnu.org
Subject: bug#62524: Support displaying all package maintainers
Date: Wed, 05 Apr 2023 16:50:49 +0200 [thread overview]
Message-ID: <87edoyjsc6.fsf@bernoul.li> (raw)
In-Reply-To: <20230329153214.752-1-jonas@bernoul.li>
[ I am re-sending this message because the MDS refused to deliver
the previous iteration.
Stefan, your reply contained a header "Cc: ??@debbugs.gnu.org". ]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Even once all ELPAs have been updated to include `:maintainers', they
>> have to continue to also include `:maintainer', for the benefit of
>> older versions of this function / package.el / Emacs.
>
> We could drop `:maintainer` within a few years, tho: this info is not
> super-important and it would impact only users of older Emacsen.
That's the plan.
>> To avoid this duplication, `package' would have to be distributed on
>> GNU ELPA as a "core" package.
>
> That still wouldn't help those users who didn't upgrade their built-in
> `package.el`.
I hope that we can eventually not only make Package available on GNU
Elpa, but also get users of older Emacs releases to update to that
version, see 87tty24ap2.fsf@bernoul.li
> Other than that: OK with me.
So should I go ahead and install this now (on master, I assume)?
Once that is done, I'll update the elpa-admin equivalent for Melpa. I
plan to only include :maintainers in archive-contents if there actually
are multiple maintainers. That way there is less duplicated data, and
I recommend you do the same in elpa-admin.
Oh, and the comment you added to package-buffer-info in 4e6f98cd505ed56
is wrong; shall I just replace "single string" with "single cons-cell"?
Cheers,
Jonas
next prev parent reply other threads:[~2023-04-05 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 15:32 bug#62524: [PATCH] Support displaying all package maintainers Jonas Bernoulli
2023-03-29 16:39 ` Jonas Bernoulli
2023-04-05 14:50 ` Jonas Bernoulli [this message]
[not found] ` <jwvpm8rv0fv.fsf-monnier+emacs@gnu.org>
[not found] ` <87o7o2jz5j.fsf@bernoul.li>
[not found] ` <jwv8reypdd2.fsf-monnier+emacs@gnu.org>
2023-04-27 21:23 ` Jonas Bernoulli
2023-05-01 2:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 19:36 ` Stefan Kangas
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=87edoyjsc6.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=62524@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).