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

Federico Beffa <beffa@ieee.org> skribis:

> 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

OK, interesting.

> 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.

IMO the ideal would have to have it split into a bunch of packages or
package outputs, like “core”, “doc”, “extra.”  Ideally, users could
choose to install 1, 2, or 3 of these and things would just work.

I’m not really knowledgeable but that seemed extremely difficult to
achieve (Andreas might want to share his sufferings ;-)).  Part of the
reason is that there’s no simple search path mechanism, and instead
something sophisticated that includes texmf.cnf and a couple of
libraries and commands to deal with search paths.

The latter prevents the addition of a “doc” output, for instance,
because the ‘texdoc’ command (in “out”) needs to refer to the “doc”
output, and vice versa (there cannot be circular references among
outputs of a derivation.)

Anyway, I think everyone would love a better solution, so if you have
ideas, do not hesitate.  :-)

Thanks,
Ludo’.

  reply	other threads:[~2015-03-25 21:17 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   ` Texlive Federico Beffa
2015-03-25 21:17     ` Ludovic Courtès [this message]
  -- 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=87bnjgg4jt.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=beffa@ieee.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).