all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: TeX Live 2019 wanted
Date: Mon, 16 Dec 2019 19:57:14 +0100	[thread overview]
Message-ID: <20191216185714.GA6488@jurong> (raw)
In-Reply-To: <871rt6enh0.fsf@devup.no>

Hello,

On Sat, Dec 14, 2019 at 08:06:19PM +0100, Marius Bakke wrote:
> Ricardo, do you think you'll have time for a TeX Live 2019 update in the
> coming weeks?  If not, could you outline the required changes for
> enterprising Guix contributors?

before your mail I had already tried to update the monolithic texlive, but
one of the patches did not apply any more; since I did not know what they
were for, I pushed it to the back of the queue. From what you write, I
suppose the patches could simply be dropped?

Then I was unsure how updating the texlive sources would impact the
modular texlive packages. Is anything special needed?

Andreas

  parent reply	other threads:[~2019-12-16 18:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14 19:06 TeX Live 2019 wanted Marius Bakke
2019-12-14 21:33 ` Pierre Neidhardt
2019-12-16 18:57 ` Andreas Enge [this message]
2019-12-16 19:49   ` Andreas Enge
2019-12-16 20:38     ` Marius Bakke
2019-12-16 22:20       ` Ricardo Wurmus
2019-12-16 22:41       ` Marius Bakke
2019-12-27 10:05         ` Andreas Enge
2020-01-09 22:10           ` Marius Bakke
2020-01-11 23:13             ` Marius Bakke
2020-01-12 10:13               ` Pierre Neidhardt
2020-01-12 10:40                 ` Ricardo Wurmus
2020-01-12 13:19                   ` Pierre Neidhardt
2020-01-12 14:49                     ` Ricardo Wurmus
2020-01-12 15:00                       ` Pierre Neidhardt
     [not found]                   ` <87blr3f4v0.fsf@kryshen.net>
2020-01-17  8:53                     ` Ricardo Wurmus
2020-01-21 10:25                       ` Marco van Hulten
2021-02-02 14:25                       ` bug#39160: " Maxim Cournoyer
2020-01-17 12:13               ` Ricardo Wurmus
2020-01-17 14:02                 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191216185714.GA6488@jurong \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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 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.