From: John Darrington <john@darrington.wattle.id.au>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: Rename texlive to tex.
Date: Tue, 24 May 2016 18:09:54 +0200 [thread overview]
Message-ID: <20160524160954.GA20389@jocasta.intra> (raw)
In-Reply-To: <87lh2zsufx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]
On Tue, May 24, 2016 at 10:59:14AM +0200, Roel Janssen wrote:
John Darrington writes:
> On Tue, May 24, 2016 at 12:14:59AM +0200, Roel Janssen wrote:
> * gnu/local.mk (GNU_SYSTEM_MODULES): Rename texlive.scm to tex.scm.
> * gnu/packages/texlive.scm: Rename file to tex.scm.
> * gnu/packages/tex.scm: Renamed from texlive.scm.
> * gnu/packages/algebra.scm: Rename texlive to tex.
> * gnu/packages/docbook.scm: Rename texlive to tex.
> * gnu/packages/engineering.scm: Rename texlive to tex.
> * gnu/packages/gettext.scm: Rename texlive to tex.
> * gnu/packages/gnome.scm: Rename texlive to tex.
> * gnu/packages/lisp.scm: Rename texlive to tex.
> * gnu/packages/maths.scm: Rename texlive to tex.
> * gnu/packages/music.scm: Rename texlive to tex.
> * gnu/packages/ocaml.scm: Rename texlive to tex.
> * gnu/packages/plotutils.scm: Rename texlive to tex.
> * gnu/packages/python.scm: Rename texlive to tex.
> * gnu/packages/scheme.scm: Rename texlive to tex.
>
> What is the purpose of doing that? I thought that texlive was the chosen
> name that the project had.
>
> I think there are a few other implementations of TeX in the wild (though
> mostly unmaintained). Furthermore, I think Knuth has a trademark on the word "tex".
>
> J'
See this thread:
https://lists.gnu.org/archive/html/guix-devel/2016-05/msg00702.html
I want to add Texmaker (an editor for TeX). Putting it in texlive.scm
wouldn't really fit because it's not part of Texlive. So, the idea is
to put everything TeX-related into one file (tex.scm).
Oh I see. I thought you were renaming the package itself, not the file in which
its definition resides (saying "Rename texlive.scm to tex.scm" would have
made this clearer).
J'
--
Avoid eavesdropping. Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-05-24 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160524050755.GA14800@jocasta.intra>
2016-05-24 8:59 ` [PATCH 1/2] gnu: Rename texlive to tex Roel Janssen
2016-05-24 16:09 ` John Darrington [this message]
2016-05-24 16:16 ` Roel Janssen
2016-05-24 18:50 ` Eric Bavier
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=20160524160954.GA20389@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=roel@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).