From: Mathieu Lirzin <mthl@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: How to compile LaTeX with 'hyperref' package?
Date: Tue, 23 Jan 2018 14:17:58 +0100 [thread overview]
Message-ID: <87607s90jd.fsf@gnu.org> (raw)
In-Reply-To: <87wp09ytg9.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 23 Jan 2018 07:34:14 +0100")
Hello Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
>> Mathieu Lirzin <mthl@gnu.org> writes:
>>
>>> I will try with ‘texlive-full’ to see if things work better.
>>
>> s/texlive-full/texlive
>>
>> The installation was quicker that I expect since it was already
>> compiled. I confirm that compiling with ‘texlive’ succeed since
>> ‘hyperref.sty’ is found directly in ‘texlive’ store output directory.
>>
>> Maybe the environment variable TEXINPUTS should be generated in
>> “~/.guix-profile/etc/profile”?
>>
>> Shall I open a bug for this?
>
> That’s not necessary as the broken up texlive-* packages are currently
> not sufficient to build a usable Texlive subset in a profile. I’m
> working on a profile hook, which is similar to what the texlive-union
> procedure does.
>
> I consider this to be the same as bug 27217.
I agree.
Thanks for pointing me to this bug.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
prev parent reply other threads:[~2018-01-23 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 11:53 How to compile LaTeX with 'hyperref' package? Mathieu Lirzin
2018-01-22 12:11 ` Mathieu Lirzin
2018-01-23 6:34 ` Ricardo Wurmus
2018-01-23 13:17 ` Mathieu Lirzin [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=87607s90jd.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=help-guix@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.
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).