unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 27217@debbugs.gnu.org
Subject: bug#27217: texlive is too big
Date: Tue, 23 Jan 2018 14:20:54 +0100	[thread overview]
Message-ID: <871sig90eh.fsf@gnu.org> (raw)
In-Reply-To: <87tw3w7v1m.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 03 Jun 2017 21:03:49 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> What’s missing?
>
> Currently, one needs to set a lot of environment variables to use these
> separate packages.  For “fastcap” I needed to set “DVIPSHEADERS” (to
> find “tex.pro”), “TFMFONTS” (for compiled metafont files), “TEXFORMATS”
> (for the compiled “latex.fmt”), and “TEXINPUTS” (for all directories
> containing tex source files).  Setting these variables manually is
> really tedious.
>
> How can we set them automatically?  A simple idea is to provide a
> procedure “texlive-union” that takes texlive packages and produces a
> wrapped variant of the tools in “texlive-bin” that run inside an
> environment where these variables are set.

After reading, it is not clear to me why having all the environment
variables set in “~/.guix-profile/etc/profile” is not good enough, or
not possible?

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

  parent reply	other threads:[~2018-01-23 13:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 19:03 bug#27217: texlive is too big Ricardo Wurmus
2017-11-23 20:51 ` bug#27217: break up TeXlive for guix Matt Wette
2018-01-23 13:20 ` Mathieu Lirzin [this message]
2018-05-28 12:02   ` bug#27217: texlive is too big Ricardo Wurmus
2018-05-28 11:07 ` Peter Neidhardt
2018-05-28 11:58   ` Ricardo Wurmus
2018-05-28 12:53     ` Peter Neidhardt
2018-12-15 14:11       ` Pierre Neidhardt
2019-01-10  9:27       ` Ludovic Courtès
2019-01-10  9:49         ` Pierre Neidhardt
2019-01-10 12:30           ` Ricardo Wurmus
2019-01-10 12:51             ` Pierre Neidhardt
2019-01-10 15:34               ` Ricardo Wurmus
2019-01-10 16:01                 ` Pierre Neidhardt
2019-01-10 16:11                   ` Ricardo Wurmus
2019-01-10 17:47                     ` Pierre Neidhardt
2019-01-10 18:50                       ` Ricardo Wurmus
2019-01-10 18:56                         ` Pierre Neidhardt
2019-01-10 19:01                           ` Ricardo Wurmus
2019-01-10 11:27         ` Ricardo Wurmus
2019-01-10 12:15           ` Ludovic Courtès
2019-01-13 12:21             ` Ricardo Wurmus
2019-01-17  9:36               ` Ludovic Courtès
2019-01-17  9:41                 ` Pierre Neidhardt
2019-01-17 10:39                   ` Ricardo Wurmus
2019-01-17 10:43                     ` Pierre Neidhardt
2019-01-17 11:01                       ` Ricardo Wurmus
2019-03-02 14:13                         ` Pierre Neidhardt
2019-03-03 14:32                           ` Jelle Licht
2019-03-05  8:39                             ` Pierre Neidhardt
2019-03-16 12:59                               ` Pierre Neidhardt
2019-03-18  8:47                                 ` Ludovic Courtès
2019-03-19 21:36                                   ` Ricardo Wurmus
2019-03-20  7:47                                     ` Pierre Neidhardt
2019-03-22 21:01                                       ` Ludovic Courtès
2019-01-17 10:36                 ` Ricardo Wurmus
2019-01-15 15:34 ` Ricardo Wurmus

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=871sig90eh.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=27217@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).