all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Texlive
Date: Sun, 15 Mar 2015 11:48:24 +0100	[thread overview]
Message-ID: <20150315104707.GA8872@debian> (raw)
In-Reply-To: <CAKrPhPPY-jx_Yeh-qwYOXsgibtUmRN_JEUeODd_wKkSiXw1u3w@mail.gmail.com>

On Sun, Mar 15, 2015 at 10:50:05AM +0100, Federico Beffa wrote:
> If I understand correctly then the two packages, texlive and
> texlive-small, will essentially be independent.

Yes, and mutually exclusive: If you install both, then there will be lots
of collisions with an unpredictable outcome.

> It would be nice to have an incremental strategy with a hierarchy, say
> texlive-base, texlive-common, texlive-extra, texlive-all, where each
> package is non-overlapping with other ones. Then a new functionality to
> aggregate packages into a new package where you specify which packages
> to include. Something like
> guix package --aggregate texlive --with texlive-base texlive-common ...

I agree, but did not find a way of doing it. The problem with texlive is
that part of the aggregation takes place in the install location (which for
us would be the store).

For instance, "mktexlsr" creates a file
  /gnu/store/pvhfl19r2v7fn00g45jkv32n211bk90h-texlive-2014/share/texmf-dist/ls-R
(after applying the patch), which contains the result of running "ls -R"
inside the directory. This could be done inside the user profile, but not
with the current setup, where
  $HOME/.guix-profile/share/texmf-dist is a link to the store directory
(which is a useful feature we added at some point in time, since it avoids
the need for symlinking the thousands of files inside this directory tree),
so that the ls-R file would be tried to be created in the store.

Then there are the calls to updmap-sys and fmtutil-sys, which I did not
look at in more detail. The latter seems to create files
texmf-var/web2c/*.fmt; it may be possible to create them by chunks and to
merge them in the profile (and then do the "ls -R"-business).

In non-functional (:-)) distributions, the problem is solved by recreating
a global configuration upon installation of an additional package.

So there may be better ways, and anybody is welcome to look into them!
My patch makes a first step by separating things better.

Andreas

  reply	other threads:[~2015-03-15 10:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15  9:50 Texlive Federico Beffa
2015-03-15 10:48 ` Andreas Enge [this message]
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     ` 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
2013-02-03 16:56 Texlive Andreas Enge
2013-02-03 18:30 ` Texlive Ludovic Courtès
2013-02-05 17:04   ` Texlive Andreas Enge
2013-02-05 17:11     ` Texlive Andreas Enge
2013-02-05 21:03     ` Texlive Ludovic Courtès
2013-02-05 22:03       ` Texlive Andreas Enge
2013-02-05 22:51         ` Texlive Ludovic Courtès
2013-02-05 19:30   ` Texlive Andreas Enge
2013-02-05 21:11     ` Texlive Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=20150315104707.GA8872@debian \
    --to=andreas@enge.fr \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.