unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Federico Beffa <beffa@ieee.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Texlive
Date: Mon, 23 Mar 2015 12:06:26 +0100	[thread overview]
Message-ID: <CAKrPhPNM6VchdG+_k_8zwRAhovgH64uDxUwFvBEo_BcUiufehQ@mail.gmail.com> (raw)
In-Reply-To: <87a8zc51hv.fsf@gnu.org>

On Mon, Mar 16, 2015 at 5:51 PM, Ludovic Courtès <ludo@gnu.org> wrote:

> I think the problem here is really that TeX Live is monolithic, and I
> don’t think that should be addressed by the packaging tools themselves.

The main TeX Live installer may make it look like it is monolithic,
but it isn't monolithic at all. It is very configurable and every user
can add his own classes, fonts, packages, ... wherever he wants even
using central installations on traditional UNIX systems. TeX Live has
its own management tool 'tlmgr', but underneath it makes use of
established Web2C tools.

As one example, setting
export TEXINPUTS=~/.guix-profile/share/texmf:

all the files in the personal profile would be found (on top of the
ones in the central installation configuration files). You can even
specify if you want to make use of files databases (ls-R), or not (and
that for each directory tree individually). See, e.g.,

http://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-540007

Making the various TeX tools find components (classes, fonts, ...) in
"extra" store locations may be tricky, but making it find them once
installed in a user profile should be easy.

Maybe finding files in "extra" store directories could be achieved by
making use of variables expansion, something like
"!!/gnu/store//share/texmf" (note the double slash and exclamation
marks), in the central configuration file. (See above document.)

I think that working out the proper way to install it on Guix may be
tricky, but, given the flexibility, a good hierarchical solution
should be possible.

Regards,
Fede

  reply	other threads:[~2015-03-23 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15  9:50 Texlive Federico Beffa
2015-03-15 10:48 ` Texlive Andreas Enge
2015-03-15 11:16   ` Texlive Federico Beffa
2015-03-16 18:54     ` Texlive Andreas Enge
2015-03-16 16:51 ` Texlive Ludovic Courtès
2015-03-23 11:06   ` Federico Beffa [this message]
2015-03-25 21:17     ` Texlive Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2015-03-14 21:54 Texlive Andreas Enge
2015-03-14 23:43 ` Texlive Daniel Pimentel
2015-03-15 15:33 ` Texlive Mark H Weaver
2015-03-15 19:14   ` Texlive Andreas Enge
2015-03-16 16:54 ` Texlive Ludovic Courtès
2015-03-16 18:37   ` Texlive Andreas Enge

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=CAKrPhPNM6VchdG+_k_8zwRAhovgH64uDxUwFvBEo_BcUiufehQ@mail.gmail.com \
    --to=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).