all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <ambrevar@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32428@debbugs.gnu.org
Subject: [bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.
Date: Tue, 21 Aug 2018 16:05:59 +0200	[thread overview]
Message-ID: <87bm9vak6w.fsf@gmail.com> (raw)
In-Reply-To: <87zhxgahb9.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Hello Ludo!

Well, we might have to duplicate the trick a dozen of times... :(
Until we get a better understanding of what's going on.

My limited understanding of this is that some TeXlive packages don't build the
fonts they need at install time, only at runtime.  I don't quite understand why
that is.

It's not clear to me if it's possible to build these fonts in advance.

That said, in the present state it's only required to generate the documentation
when building the package.  While this escapes the build directory, I assume
this

Hopefully we will come with a clearer answer to this issue in the future.

I'll merge considering the workaround is much better than having a full texlive
as a dependency.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-08-21 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 16:06 [bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union Pierre Neidhardt
     [not found] ` <handler.32428.B.153417644229154.ack@debbugs.gnu.org>
2018-08-13 16:10   ` Pierre Neidhardt
2018-08-20 20:55 ` Ludovic Courtès
2018-08-21 14:05   ` Pierre Neidhardt [this message]
2018-08-21 14:25     ` Pierre Neidhardt
2018-08-22 13:46     ` Ludovic Courtès
2018-08-22 13:50       ` Pierre Neidhardt
2018-08-22 14:20       ` Ricardo Wurmus
2018-08-21 14:31 ` bug#32428: " Pierre Neidhardt

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=87bm9vak6w.fsf@gmail.com \
    --to=ambrevar@gmail.com \
    --cc=32428@debbugs.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 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.