unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Thomas <jimjoe@gmx.net>
To: emacs-devel@gnu.org
Subject: Re: ELPA submission: mathjax.el
Date: Sun, 27 Oct 2024 03:33:02 +0530	[thread overview]
Message-ID: <8634kijze1.fsf@gmx.net> (raw)
In-Reply-To: <87h68zxpmo.fsf@gmail.com> (Augusto Stoffel's message of "Sat, 26 Oct 2024 09:57:51 +0200")

Augusto Stoffel wrote:

>>   > B. If the build environment can run containers, I can include a
>>   > suitable Dockerfile.
>>
>> Container systems in general present the same kind of pitfalls as npm:
>> they put lots of free modules and lots of nonfree modules into a
>> bucket and making sure you don't pull out any of the nonfree ones is
>> your problem.
>
> That's correct.  But note that when your container declaration starts
> with
>
>   FROM docker.io/debian:stable
>
> then you know you're just running on an isolated copy of Debian stable.
> You have access to exactly the same nonfree software you could get in
> the ELPA build system itself (which runs Debian stable).
>
>> I've been told there are important differences between the well-known
>> container systems in this regard, and I don't remember how Docker
>> stacks up.  MAYBE if we consult a Docker expert we will find it can be
>> used safely.  But we had better study this carefully.
>>
>> System distributions include binary packages to speed installation.
>> We can surely package mathjax this way somehow or other.  But we must
>> release sources with a build recipe too.  If we include mathjax
>> somehoe in Emacs, or in GNU in any way, we _must_ include a way to
>> build it from source.  That includes any special tools it needs.
>>
>> If the makefile to compile mathjax uses a container, it had better
>> include the rules to build that container, manually specifying which
>> modules to include in the container.  Somewhere there must be rules to
>> rebuild THOSE modules from source.
>
> I've just mentioned containers as a hypothetical technical solution,
> it's not being considered seriously.

In any case, there seems to be a Guix package for it:

  https://packages.guix.gnu.org/packages/js-mathjax/

So it should be trivial to make a 'free' container out of.

--



  reply	other threads:[~2024-10-26 22:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26  7:57 ELPA submission: mathjax.el Augusto Stoffel
2024-10-26 22:03 ` James Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-12 14:35 Augusto Stoffel
2024-10-17  3:54 ` Richard Stallman
2024-10-17  4:27   ` Augusto Stoffel
2024-10-23  7:23 ` Philip Kaludercic
2024-10-23 14:02   ` Stefan Kangas
2024-10-23 15:28     ` Augusto Stoffel
2024-10-23 19:04       ` Philip Kaludercic
2024-10-26  5:46         ` Richard Stallman
2024-10-27  5:09           ` Richard Stallman
2024-10-26  5:46       ` Richard Stallman
2024-10-23 15:35   ` Augusto Stoffel

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=8634kijze1.fsf@gmx.net \
    --to=jimjoe@gmx.net \
    --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).