From: "Mattias Engdegård" <mattiase@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Package proposal: relint (ex-trawl)
Date: Tue, 19 Mar 2019 21:30:21 +0100 [thread overview]
Message-ID: <B4536FA9-4B4C-447A-8D98-D60842E0BA20@acm.org> (raw)
In-Reply-To: <83tvfyu4cx.fsf@gnu.org>
19 mars 2019 kl. 19.05 skrev Eli Zaretskii <eliz@gnu.org>:
>>
>> The plan is still to integrate it with Emacs `make check' in some way, unless the developers dislike Makefile rules that use locally-installed external packages. It will not be mandatory.
>
> If relint will be part of "make check", I think we'd want it in the
> Emacs repository (only there or in addition to ELPA), so that one
> could run the full test suite even when off-line.
Then xr would have to be moved into the Emacs tree as well, since relint requires that package.
Just to clarify, since you mentioned "off-line": I do not propose any build step that would fetch anything over the network. An optional 'make check' step would not, I though, be different from optional libraries used in the build.
next prev parent reply other threads:[~2019-03-19 20:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 13:24 [ELPA] Package proposal: relint (ex-trawl) Mattias Engdegård
2019-03-19 18:05 ` Eli Zaretskii
2019-03-19 20:30 ` Mattias Engdegård [this message]
2019-03-19 21:43 ` Stefan Monnier
2019-03-20 5:52 ` Eli Zaretskii
2019-03-20 13:08 ` Stefan Monnier
2019-03-20 13:25 ` Eli Zaretskii
2019-03-21 11:19 ` Mattias Engdegård
2019-03-21 14:26 ` Eli Zaretskii
2019-03-22 14:17 ` Mattias Engdegård
2019-03-22 14:31 ` Stefan Monnier
2019-03-22 14:49 ` Eli Zaretskii
2019-03-22 15:01 ` Stefan Monnier
2019-03-22 15:20 ` Eli Zaretskii
2019-03-22 15:49 ` Stefan Monnier
2019-03-22 16:12 ` Stefan Monnier
2019-03-22 18:18 ` Stefan Monnier
2019-03-22 18:36 ` T.V Raman
2019-03-23 2:33 ` Richard Stallman
2019-03-26 14:14 ` Mattias Engdegård
2019-03-26 16:00 ` Eli Zaretskii
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=B4536FA9-4B4C-447A-8D98-D60842E0BA20@acm.org \
--to=mattiase@acm.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).