From: "J.P." <jp@neverwas.me>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56340@debbugs.gnu.org, Amin Bandali <bandali@gnu.org>,
dick.r.chiang@gmail.com, emacs-erc@gnu.org
Subject: bug#56340: Change erc dependencies
Date: Tue, 06 Sep 2022 06:54:18 -0700 [thread overview]
Message-ID: <87mtbc38xh.fsf@neverwas.me> (raw)
In-Reply-To: <875yi1zkdu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 05 Sep 2022 21:33:33 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> "J.P." <jp@neverwas.me> writes:
>
>> [1] If we did stick with a new file, what's the best name for such a
>> thing? I just went with `erc-common', for now, but perhaps something
>> ending in -macs or -core would be more faithful to the platform?
>
> erc-common is fine.
Cool, thanks.
BTW (for anyone who cares), I'm pretty sure going this route would mean
having to update ERC's ELPA recipe. Actually, since we'll likely be
adding more files later this year (SASL, for one), it might be prudent
to just take care of that now, regardless.
Bandali added the original entry, so he's probably better equipped to
handle this, but rather than list the entire manifest, what about doing
something like this?
:core ("lisp/erc/"
"doc/emacs/doclicense.texi"
"doc/emacs/docstyle.texi"
"doc/misc/erc.texi"
"etc/ERC-NEWS"
"COPYING")
:excludes ("lisp/erc/erc-loaddefs.el" "lisp/erc/ChangeLog.*")
I tried the above with a local checkout of ELPA, and it seemed to build
all right. But, as usual, I don't know what I'm doing.
next prev parent reply other threads:[~2022-09-06 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 15:23 bug#56340: 29.0.50; [PATCH] Don't ask people to order requires dick.r.chiang
2022-07-02 12:32 ` Lars Ingebrigtsen
2022-07-04 23:36 ` J.P.
[not found] ` <87czekcuxj.fsf@neverwas.me>
2022-07-05 1:59 ` dick
2022-07-05 6:39 ` bug#56340: Change erc dependencies J.P.
[not found] ` <87sfng83n8.fsf_-_@neverwas.me>
2022-07-16 14:17 ` J.P.
[not found] ` <877d4d9m6c.fsf@neverwas.me>
2022-09-05 19:33 ` Lars Ingebrigtsen
[not found] ` <875yi1zkdu.fsf@gnus.org>
2022-09-06 13:54 ` J.P. [this message]
2022-09-06 14:03 ` Lars Ingebrigtsen
[not found] ` <87tu5kr45x.fsf@gnus.org>
2022-10-12 2:52 ` bug#56340: Change erc dependencies (ELPA question) J.P.
[not found] ` <875ygp3g9j.fsf_-_@neverwas.me>
2022-10-12 17:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <jwv4jw9lz5z.fsf-monnier+emacs@gnu.org>
2022-10-13 2:49 ` 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=87mtbc38xh.fsf@neverwas.me \
--to=jp@neverwas.me \
--cc=56340@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=emacs-erc@gnu.org \
--cc=larsi@gnus.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 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.