all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 31850@debbugs.gnu.org
Subject: [bug#31850] [PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs".
Date: Sun, 17 Jun 2018 13:44:11 +0200	[thread overview]
Message-ID: <87efh563jo.fsf@mdc-berlin.de> (raw)
In-Reply-To: <cu7in6hsxif.fsf@systemreboot.net>


Arun Isaac <arunisaac@systemreboot.net> writes:

>>> ‘texlive-bin’ has just 252 dependent it seems, many of which are
>>> ‘texlive-’ packages, which are usually quickly built.  So I’d say it’s
>>> OK for master, but I could be missing some other way in which
>>> ‘texlive-bin’ is depended on.
>
> But, we'd be forcing people to download the huge (~ 2.2 GB)
> texlive-texmf source tarball. And, the texlive package which depends on
> texlive-bin spends a good deal of time in the install phase. Is this
> fine?

Only until this is built, which in the case of texlive should not take a
very long time on the build farm.

--
Ricardo

  reply	other threads:[~2018-06-17 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 19:26 [bug#31850] [PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs" Arun Isaac
     [not found] ` <handler.31850.B.15290908242382.ack@debbugs.gnu.org>
2018-06-15 19:56   ` [bug#31850] Acknowledgement ([PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs".) Arun Isaac
2018-06-16 16:13 ` [bug#31850] [PATCH] gnu: texlive-bin: Use absolute path to ghostscript executable "gs" Ludovic Courtès
2018-06-16 20:46   ` Ricardo Wurmus
2018-06-17  7:06     ` Arun Isaac
2018-06-17 11:44       ` Ricardo Wurmus [this message]
2018-06-17 16:01         ` bug#31850: " Arun Isaac

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=87efh563jo.fsf@mdc-berlin.de \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=31850@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.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.
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.