all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Jelle Licht <jlicht@fsfe.org>, 27217@debbugs.gnu.org
Subject: bug#27217: texlive is too big
Date: Fri, 22 Mar 2019 22:01:36 +0100	[thread overview]
Message-ID: <87imwa4o9b.fsf@gnu.org> (raw)
In-Reply-To: <87sgvikmwl.fsf@bababa.i-did-not-set--mail-host-address--so-tickle-me> (Pierre Neidhardt's message of "Wed, 20 Mar 2019 08:47:22 +0100")

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> So TeX Live packages would use ‘texlive-fetch’ instead of ‘svn-fetch’ or
>>> similar, right?
>>>
>>> If that’s the case, then merely computing the derivation of one of these
>>> would require fetching the tldb database, which would be problematic.
>>> Is this correct?
>>
>> I think there has been a misunderstanding here.  Pierre seems to be
>> using the name “texlive-fetch” for two different things.
>
> No, the "texlive-fetch" I meant was Ricardo's idea.  We are talking
> about the same thing.
>
>> The extraction of information from the plain text database (which is
>> included with “texlive-bin”) is done “offline” when using the importer,
>> i.e. when generating package definitions.
>
> Exactly, I think this is the part that Ludovic misunderstood.

OK, got it, thanks for explaining.

Ludo’.

  reply	other threads:[~2019-03-22 21:21 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 19:03 bug#27217: texlive is too big Ricardo Wurmus
2017-11-23 20:51 ` bug#27217: break up TeXlive for guix Matt Wette
2018-01-23 13:20 ` bug#27217: texlive is too big Mathieu Lirzin
2018-05-28 12:02   ` Ricardo Wurmus
2018-05-28 11:07 ` Peter Neidhardt
2018-05-28 11:58   ` Ricardo Wurmus
2018-05-28 12:53     ` Peter Neidhardt
2018-12-15 14:11       ` Pierre Neidhardt
2019-01-10  9:27       ` Ludovic Courtès
2019-01-10  9:49         ` Pierre Neidhardt
2019-01-10 12:30           ` Ricardo Wurmus
2019-01-10 12:51             ` Pierre Neidhardt
2019-01-10 15:34               ` Ricardo Wurmus
2019-01-10 16:01                 ` Pierre Neidhardt
2019-01-10 16:11                   ` Ricardo Wurmus
2019-01-10 17:47                     ` Pierre Neidhardt
2019-01-10 18:50                       ` Ricardo Wurmus
2019-01-10 18:56                         ` Pierre Neidhardt
2019-01-10 19:01                           ` Ricardo Wurmus
2019-01-10 11:27         ` Ricardo Wurmus
2019-01-10 12:15           ` Ludovic Courtès
2019-01-13 12:21             ` Ricardo Wurmus
2019-01-17  9:36               ` Ludovic Courtès
2019-01-17  9:41                 ` Pierre Neidhardt
2019-01-17 10:39                   ` Ricardo Wurmus
2019-01-17 10:43                     ` Pierre Neidhardt
2019-01-17 11:01                       ` Ricardo Wurmus
2019-03-02 14:13                         ` Pierre Neidhardt
2019-03-03 14:32                           ` Jelle Licht
2019-03-05  8:39                             ` Pierre Neidhardt
2019-03-16 12:59                               ` Pierre Neidhardt
2019-03-18  8:47                                 ` Ludovic Courtès
2019-03-19 21:36                                   ` Ricardo Wurmus
2019-03-20  7:47                                     ` Pierre Neidhardt
2019-03-22 21:01                                       ` Ludovic Courtès [this message]
2019-01-17 10:36                 ` Ricardo Wurmus
2019-01-15 15:34 ` Ricardo Wurmus

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=87imwa4o9b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27217@debbugs.gnu.org \
    --cc=jlicht@fsfe.org \
    --cc=mail@ambrevar.xyz \
    /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.