unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: 32428@debbugs.gnu.org
Subject: [bug#32428] [PATCH] gnu: mit-scheme: Use minimal texlive-union.
Date: Mon, 20 Aug 2018 22:55:54 +0200	[thread overview]
Message-ID: <87zhxgahb9.fsf@gnu.org> (raw)
In-Reply-To: <20180813160643.15076-1-ambrevar@gmail.com> (Pierre Neidhardt's message of "Mon, 13 Aug 2018 18:06:43 +0200")

Hello Pierre!

Pierre Neidhardt <ambrevar@gmail.com> skribis:

> * gnu/packages/scheme.scm (mit-scheme)[native-inputs]: Replace texlive with texlive-union.
> ---
>  gnu/packages/scheme.scm | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/gnu/packages/scheme.scm b/gnu/packages/scheme.scm
> index b30245cce..ef94aedad 100644
> --- a/gnu/packages/scheme.scm
> +++ b/gnu/packages/scheme.scm
> @@ -104,6 +104,10 @@
>                                 (find-files "src/compiler" "^make\\.")))
>               (chdir "src")
>               #t))
> +         ;; FIXME: the texlive-union insists on regenerating fonts.  It stores
> +         ;; them in HOME, so it needs to be writeable.
> +         (add-before 'build 'set-HOME
> +           (lambda _ (setenv "HOME" "/tmp") #t))

Is this a bug in ‘texlive-union’?  Does it take time and space to
regenerate the fonts?

Otherwise the change LGTM, for ‘emacs-ess’ & co. as well, as long as we
don’t duplicate the $HOME trick dozens of times.

Thanks!

Ludo’.

  parent reply	other threads:[~2018-08-20 20:57 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 [this message]
2018-08-21 14:05   ` Pierre Neidhardt
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

  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=87zhxgahb9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32428@debbugs.gnu.org \
    --cc=ambrevar@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. 
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).