unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Oliver <p.d.oliver@mavit.org.uk>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Grammar checking in Emacs
Date: Fri, 19 Nov 2021 22:14:24 +0000 (GMT)	[thread overview]
Message-ID: <701918d9-1a6c-75bf-332b-d4f0b7489d2@froglet.home.mavit.org.uk> (raw)
In-Reply-To: <E1mnCKU-0004uo-G3@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

On Tue, 16 Nov 2021, Richard Stallman wrote:

>  > > AFAICT the most popular way to install it is as a "snap" package, which
>  > > I consider to be a euphemism for a blob :-(
>
>  > You can unzip prebuilt JARs from https://languagetool.org/download/LanguageTool-stable.zip, which seems simpler but similarly blobby.
>
> In principle, those JARs could make it easier to see the full list of
> contents and determine what nonfree files there are, if any.  But it
> looks like you don't think so.  Would you please expand on why you
> don't think so?

I was thinking only about our ability to modify the contents.

If a reputable GNU/Linux distribution includes a software package, then we can be sure that it’s known how to reproducibly build it from source.  If it becomes too hard for distributions to build from source, and people come to rely on developer-supplied pre-built artefacts instead (be they binaries, bytecode, container images, or whatever the next thing is), then I would be less confident.

My main point was to draw attention to the availability of the JARs.  The mention of blobbyness was only intended as a throwaway aside, to be honest.

-- 
Peter Oliver

  reply	other threads:[~2021-11-19 22:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m1zgq6xon7.fsf.ref@yahoo.es>
2021-11-15  0:12 ` Grammar checking in Emacs Daniel Martín
2021-11-15  2:46   ` Stefan Monnier
2021-11-15  8:16     ` tomas
2021-11-15 22:43     ` Peter Oliver
2021-11-15 23:02       ` Stefan Monnier
2021-11-16 18:01         ` Philip Kaludercic
2021-11-16 18:09           ` Eli Zaretskii
2021-11-17  3:18           ` Stefan Monnier
2021-11-19 21:51         ` Peter Oliver
2021-11-17  4:13       ` Richard Stallman
2021-11-19 22:14         ` Peter Oliver [this message]
2021-11-16  4:06     ` Richard Stallman
2021-11-16 11:32       ` Ihor Radchenko
2021-11-16 14:28         ` Stefan Monnier
2021-11-16 22:49           ` Tim Cross
2021-11-16 23:29             ` Stefan Monnier
2021-11-16  6:28     ` Alexandre Garreau
2021-11-16 14:30       ` Stefan Monnier
2021-11-16 15:43         ` tomas
2021-11-18  3:51         ` Richard Stallman
2021-11-16  8:23     ` tomas
2021-11-15 19:45   ` Rudolf Adamkovič
2021-11-17  4:12     ` Richard Stallman

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=701918d9-1a6c-75bf-332b-d4f0b7489d2@froglet.home.mavit.org.uk \
    --to=p.d.oliver@mavit.org.uk \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).