unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Mohsin Kaleem <mohkale@kisara.moe>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Add package flymake-rest
Date: Sun, 08 May 2022 10:06:30 +0000	[thread overview]
Message-ID: <87h760uymx.fsf@posteo.net> (raw)
In-Reply-To: <87bkw8e83f.fsf@kisara.moe> (Mohsin Kaleem's message of "Sun, 08 May 2022 09:34:12 +0100")

Mohsin Kaleem <mohkale@kisara.moe> writes:

> Hi,
>
> This is just a friendly email to ask whether there's any interest in
> including my package flymake-rest <https://melpa.org/#/flymake-rest>
> in NonGNU ELPA (or ELPA). It's essentially an assortment of diagnostic
> functions for a bunch of different linters/checkers and a few helper
> functions for using flymake.
>
> I realise the README of NonGNU ELPA mentions no packages may make
> references to non-free software which could be a linter in the case of
> this package. If necessary I'll move all references to such linters to
> a separate MELPA package and only keep diagnostic functions for linters
> with free licenses in the main package being proposed to NonGNU ELPA.

Out of curiosity, do you know if such software is widespread?  I guess
we are talking about things like something like a proprietary compiler
with static analysis, right?

It should also be pointed out that the issue isn't acknowledging
non-free software in itself (my usual example is browse-url supports
Google Chrome), but a strict dependence for the package to work.  Now I
am not sure if, e.g. adding support for Intel's ICC compiler would be OK
if GCC and Clang were also provided (never used ICC so this example
might be nonsensical)?

> The purpose of this email is mostly to gauge whether there's any desire
> for this package in NonGNU ELPA. What do you think?

I certainly think that this would be a very interesting package to have
in NonGNU ELPA (or even GNU ELPA).  If you are interested, it might even
make sense to add the macros -- or some variation thereof -- you use to
generate a checker to Flymake (ie. the core) itself.  Whether or not the
checkers should also be added is a different matter.



  reply	other threads:[~2022-05-08 10:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08  8:34 [ELPA] Add package flymake-rest Mohsin Kaleem
2022-05-08 10:06 ` Philip Kaludercic [this message]
2022-05-08 10:17   ` Mohsin Kaleem
2022-05-08 19:09     ` Philip Kaludercic
2022-05-08 21:52       ` Stefan Monnier
2023-04-21 14:22         ` Mohsin Kaleem
2023-04-21 17:43           ` João Távora
2023-04-22  6:51           ` Philip Kaludercic
2023-04-22 10:27             ` Mohsin Kaleem

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=87h760uymx.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=mohkale@kisara.moe \
    /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).