unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Too many questions about texlive-texmf
Date: Tue, 12 Jul 2016 11:10:41 +0200	[thread overview]
Message-ID: <8760sbkyr2.fsf@gnu.org> (raw)
In-Reply-To: <20160711082121.GC17662@debian-netbook> (Efraim Flashner's message of "Mon, 11 Jul 2016 11:21:21 +0300")

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Mon, Jul 11, 2016 at 09:42:34AM +0200, Ricardo Wurmus wrote:
>> 
>> Leo Famulari <leo@famulari.name> writes:
>> 
>> > We don't serve substitutes of texlive-texmf. We achieve this by
>> > configuring nginx to return "410 Gone" [0].
>> >
>> > This requires users to build it with '--fallback', and the Guix error
>> > message even recommends this, but many users ask about it on IRC.
>> >
>> > I think we should mark it '#:substitutable? #f' so that, IIUC, Guix will
>> > download and build texlive-texmf from the upstream source automatically,
>> > without stopping or requiring users to use '--fallback'.
>> 
>> Does this cause substitutes to be disabled for all packages that depend
>> on texlive-texmf?

No, it just sets a flag in the texlive-texmf derivation itself (search
for “substituable?” in (guix derivations)).

> Based on the notes in maths.scm on
> openblas, `#:substitutable? #f' also disables offloading,

I don’t see this comment, but this bug was fixed last year:
<http://bugs.gnu.org/18747>.  :-)

So I think Leo’s suggestion is a good one.  I believe only texlive-texmf
itself needs #:substitutable? #f.

Thoughts?

Ludo’.

  parent reply	other threads:[~2016-07-12  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 18:51 Too many questions about texlive-texmf Leo Famulari
2016-07-11  7:42 ` Ricardo Wurmus
2016-07-11  8:21   ` Efraim Flashner
2016-07-11 10:25     ` ng0
2016-07-11 16:50     ` Leo Famulari
2016-07-12  9:10     ` Ludovic Courtès [this message]
2016-07-11 16:40   ` Leo Famulari

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=8760sbkyr2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@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 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).