From: Andreas Enge <andreas@enge.fr>
To: Myles English <mylesenglish@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: using texlive class from a private texmf tree
Date: Sun, 8 Dec 2019 15:30:05 +0100 [thread overview]
Message-ID: <20191208143005.GA6426@jurong> (raw)
In-Reply-To: <877e39snb8.fsf@gmail.com>
Hello,
On Fri, Dec 06, 2019 at 11:31:07AM +0000, Myles English wrote:
> These are the packages installed:
>
> $ guix package -I | grep tex
> texlive 20180414 out /gnu/store/wlba9v03ypi0z5qz7p89sa0w12lh37zb-texlive-20180414
> texlive-bin 20180414 out /gnu/store/znf7mmx3vslsscn9v3ilxmgkirqwswy8-texlive-bin-20180414
> texlive-base 49435 out /gnu/store/5qg546zydvcjcqvbf7d49yg4iq7yhn9d-texlive-base-49435
>
> Here are the relevant environment variables:
>
> $ env | grep TEX
> TEXMF=/home/myles/.guix-profile/share/texmf-dist
> TEXMFCNF=/home/myles/.guix-profile/share/texmf-dist/web2c
>
> Is there anything else I can try?
maybe try to exactly mimick my environment? And if that does not help,
I would not know where to look next.
$ guix package -I | grep tex
texlive 20180414 out /gnu/store/axddwjmfip84lz3fp7xqh9p9vx8hchcm-texlive-20180414
In particular, I think that texlive-base (from the split-up texlive
distribution) and texlive-bin (from the monolithic one, but also included
in the "meta-package" texlive) will collide.
$ env | grep TEX
There should be nothing. Maybe that is also pulled in from the split-up
package installed into the profile?
If it works with the monolithic, but not the split-up package, then it is
a bug to be reported.
Andreas
prev parent reply other threads:[~2019-12-08 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 13:36 using texlive class from a private texmf tree Myles English
2019-12-04 20:33 ` Andreas Enge
2019-12-06 11:31 ` Myles English
2019-12-08 14:30 ` Andreas Enge [this message]
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=20191208143005.GA6426@jurong \
--to=andreas@enge.fr \
--cc=help-guix@gnu.org \
--cc=mylesenglish@gmail.com \
/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.
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).