unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brendan Tildesley <brendan.tildesley@openmailbox.org>
To: guix-devel@gnu.org
Subject: Re: Packaging mathjax and other javascript libraries
Date: Sun, 28 May 2017 23:26:34 +1000	[thread overview]
Message-ID: <dd97e1d9-54b4-8708-3f9f-1cd166a2561b@openmailbox.org> (raw)
In-Reply-To: <87shjsf2vu.fsf@elephly.net>

Ricardo Wurmus 於 2017-05-26 18:17 寫道:
> Arun Isaac <arunisaac@systemreboot.net> writes:
>
> [...]
> I would be in favour of doing it the Debian way.  It’s difficult to draw
> a line between a web application and a JavaScript library, so I’d rather
> not have to make a decision like that each time we package something
> written in JavaScript.
>
>> Should we have any prefix in the package name for javascript libraries
>> such as mathjax? Apparently, Debian uses the "libjs-" prefix. Also, it
>> might be a good idea to have a separate file
>> (gnu/packages/javascript.scm) for these javascript libraries.
> So far we have separated packages according to their purpose.  There are
> a few exceptions, such as python.scm, which would best be split up.  If
> possible I’d rather have JavaScript libraries in modules that indicate
> what their purpose is.  General purpose frameworks, on the other hand,
> could very well fit in a javascript.scm.
>
I also wondered if mathjax should be broken up into js-mathjax and
font-mathjax, since it is 180MiB or so. Some distros even just delete
some of the fonts.

  parent reply	other threads:[~2017-05-28 13:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 17:00 Packaging mathjax and other javascript libraries Arun Isaac
2017-05-25 18:20 ` Pjotr Prins
2017-05-26  8:17 ` Ricardo Wurmus
2017-05-27 18:56   ` Arun Isaac
2017-05-27 21:17     ` Ricardo Wurmus
2017-05-28  6:03       ` Arun Isaac
2017-05-28 13:26   ` Brendan Tildesley [this message]
2017-05-28 18:45     ` Arun Isaac

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd97e1d9-54b4-8708-3f9f-1cd166a2561b@openmailbox.org \
    --to=brendan.tildesley@openmailbox.org \
    --cc=guix-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/guix.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).