From: Amin Bandali <bandali@gnu.org>
To: "J.P." <jp@neverwas.me>
Cc: emacs-erc@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
68660@debbugs.gnu.org
Subject: bug#68660: 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode
Date: Sat, 27 Jan 2024 15:30:15 -0500 [thread overview]
Message-ID: <8734uiwmco.fsf__4900.79293247021$1706387485$gmane$org@gnu.org> (raw)
In-Reply-To: <877cjyaa31.fsf@neverwas.me>
J.P. writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>>>> I can see several ways to "fix" this, but I think the simplest would be
>>> Would one of those several ways possibly include overriding the
>>> `package-desc-extras' :maintainer item scraped by `lm-maintainers' with
>>> a spec item from an elpa-packages entry? I see that support for a
>>> `:maintainer' keyword was recently added, but it appears to serve some
>>> other purpose. Anyway, I've attached a sketch of what I'm trying to
>>> describe, but I'm rather unfamiliar with this program.
>>
>> Hmm... this requires manual work per package, and it drops support for
>> multiple maintainers altogether, so I'd rather not go there. I was
>> thinking instead of making `:maintainer` hold only a single item (the
>> improper list thingy) and use `:maintainers` to hold the list of
>> maintainers when there's more than one, which would be more
>> backward compatible and would solve the problem for all packages.
>
> Yes, what you describe definitely seems preferable. So, I guess
> `:maintainer' (singular) will always be populated no matter what, for
> the benefit of legacy clients who only speak the one. And newer clients
> will be taught to always first check `:maintainers' (plural).
>
> Please let me know if anything is required from ERC to make this a
> reality. And, of course, I very much appreciate your taking the time.
>
Sorry I'm a bit out of the loop & probably missing some context here.
I think I'd prefer to keep the personal names in ERC's Maintainer(s)
field if possible, but if it's too much of a hassle and/or impossible
then of course that's a different story. I'll defer to J.P. and you
to go forward with whatever works best.
Thanks,
-a
next prev parent reply other threads:[~2024-01-27 20:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 14:56 bug#68660: 29.2; ELPA: Wrong type argument w. multiple maintainers in package-menu-mode J.P.
2024-01-22 15:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwvjzo11jh2.fsf-monnier+emacs@gnu.org>
2024-01-23 14:57 ` J.P.
[not found] ` <87o7dcm718.fsf@neverwas.me>
2024-01-23 19:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwvplxrx2be.fsf-monnier+emacs@gnu.org>
2024-01-23 22:34 ` J.P.
[not found] ` <87le8fisqg.fsf@neverwas.me>
2024-01-24 0:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwvv87jsgfz.fsf-monnier+emacs@gnu.org>
2024-01-24 1:22 ` J.P.
[not found] ` <87ede7frtz.fsf@neverwas.me>
2024-01-24 14:31 ` J.P.
[not found] ` <87y1ceby5w.fsf@neverwas.me>
2024-01-24 15:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwv5xziyc60.fsf-monnier+emacs@gnu.org>
2024-01-24 17:57 ` J.P.
[not found] ` <877cjyaa31.fsf@neverwas.me>
2024-01-27 20:30 ` Amin Bandali [this message]
2024-01-31 19:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwvr0hxtinl.fsf-monnier+emacs@gnu.org>
2024-02-01 2:52 ` J.P.
[not found] ` <87ttmssxok.fsf@neverwas.me>
2024-02-14 1:58 ` J.P.
[not found] ` <87eddfg61t.fsf@neverwas.me>
2024-02-14 16:59 ` Philip Kaludercic
[not found] ` <87a5o3gexk.fsf@posteo.net>
2024-02-14 19:15 ` J.P.
[not found] ` <877cj6eu2t.fsf@neverwas.me>
2024-02-14 20:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwvmss2lsgn.fsf-monnier+emacs@gnu.org>
2024-02-14 20:54 ` J.P.
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8734uiwmco.fsf__4900.79293247021$1706387485$gmane$org@gnu.org' \
--to=bandali@gnu.org \
--cc=68660@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.