unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [ELPA] Package proposal: relint (ex-trawl)
Date: Fri, 22 Mar 2019 16:49:06 +0200	[thread overview]
Message-ID: <83va0bq80t.fsf@gnu.org> (raw)
In-Reply-To: <11F8B0FD-DF74-4DDC-97F4-73244352DEE5@acm.org> (message from Mattias Engdegård on Fri, 22 Mar 2019 15:17:26 +0100)

> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 22 Mar 2019 15:17:26 +0100
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> 
> > If you want it on ELPA, why make a target for it in Emacs?  Why not
> > tell in the package's docs how to use it to lint Emacs regular
> > expressions?
> 
> I was asked to integrate it with 'make check', but I'm sure make somethingelse would do just as well.
> It was also suggested to me that I put it on ELPA, so why not make everyone happy.

My point was that I don't think we should have in our Makefiles
targets that require tools which are neither expected to be installed
on many systems nor come with the Emacs repository.  If people must
install add-on packages, then the glue to use those packages vis-a-vis
Emacs is better kept as part of the package.  E.g., you could have a
small Makefile in the package with a lint-emacs-regexps target.



  parent reply	other threads:[~2019-03-22 14:49 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
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 [this message]
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=83va0bq80t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --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 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).