unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>, Federico Beffa <beffa@ieee.org>
Subject: Re: texlive failure
Date: Tue, 10 Feb 2015 15:09:13 +0100	[thread overview]
Message-ID: <20150210140913.GB23477@debian> (raw)
In-Reply-To: <87bnl1swu5.fsf@netris.org>

On Tue, Feb 10, 2015 at 08:46:42AM -0500, Mark H Weaver wrote:
> I wonder if we should consider setting #:substitutable? #f for texlive.
> However, we would have to be careful not to propagate this setting, as
> was recently proposed in the "Numpy failures" thread.

I have been working on a split of texlive into two private packages,
the binaries and the data (which unfortunately depends on the binaries),
and a public one that joins the two. We could then also have a
texlive-small with a smaller data portion.

With Ludovic we have been discussing numerous solutions over the last
week, but when implementing them, something always went wrong...
I think we now have a solution that works with wrapping all binaries,
and once some changes are made in core-updates to enable this for
symbolic links, it should be easy to implement. But before it works,
I am not giving guarantees any more...

Then a possible solution would be to substitute the binary package
(which requires CPU time), but not the data package (which requires almost
none).

Andreas

  reply	other threads:[~2015-02-10 14:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 12:26 texlive failure Federico Beffa
2015-02-10 12:55 ` Ludovic Courtès
2015-02-10 12:58   ` Federico Beffa
2015-02-10 12:56 ` Federico Beffa
2015-02-10 13:34   ` Andreas Enge
2015-02-10 13:46     ` Mark H Weaver
2015-02-10 14:09       ` Andreas Enge [this message]
2015-02-10 13:50     ` Daniel Pimentel
2015-02-10 14:04       ` Andreas Enge
2015-02-10 14:37   ` Ludovic Courtès

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=20150210140913.GB23477@debian \
    --to=andreas@enge.fr \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 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).