From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Manual PDF and translation (modular texlive?)
Date: Sun, 18 Oct 2020 08:47:07 +0200 [thread overview]
Message-ID: <87d01gvxn8.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ0i_Bxub7Gk5Es_L9FFpMz1HV6L=xfHSS454dQsFN+kAg@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Ricardo,
>
> On Sat, 17 Oct 2020 at 23:55, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> It’s almost certainly due to configuration of the modular texlive.
>> We’re generating a whole bunch of font map files and encoding files
>> already, but something somewhere must still be missing.
>>
>> I embarked on a journey to fix this and am now deep into upgrading and
>> adding TeX Live packages… The first step in fixing this is to ensure
>> that all texlive-* packages contain the files that they should. The old
>> texlive-* packages consisted simply of a single directory from the big
>> TeX Live SVN repository. Since the addition of multiple SVN fetch and
>> simple-texlive-package using it I have added a whole bunch of new
>> texlive-* packages that contain all files as recorded in texlive.tlpdb.
>
> Are you planning to commit these in the wip-texlive branch?
Perhaps. I’m still in the middle of figuring things out and
experimenting. At some point I’ll probably re-create the wip-texlive
branch, though.
> Is it "reasonable" to merge before the release?
No. Changes to TeX would lead to a full rebuild.
--
Ricardo
next prev parent reply other threads:[~2020-10-18 6:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 14:50 Manual PDF and translation (modular texlive?) zimoun
2020-10-16 19:28 ` Ricardo Wurmus
2020-10-16 20:10 ` Ricardo Wurmus
2020-10-17 20:09 ` zimoun
2020-10-17 21:57 ` Ricardo Wurmus
2020-10-17 22:18 ` zimoun
2020-10-18 6:47 ` Ricardo Wurmus [this message]
2020-10-21 10:24 ` Ludovic Courtès
2020-10-21 22:10 ` Ricardo Wurmus
2020-10-22 12:02 ` Ricardo Wurmus
2020-10-22 12:50 ` Ricardo Wurmus
2020-10-22 19:52 ` Ricardo Wurmus
2020-10-22 20:20 ` zimoun
2020-10-22 20:28 ` Ricardo Wurmus
2020-10-22 20:37 ` zimoun
2020-10-22 20:36 ` Ricardo Wurmus
2020-10-22 20:40 ` zimoun
2020-10-22 20:46 ` zimoun
2020-10-22 21:59 ` Ricardo Wurmus
2020-10-25 11:07 ` Ricardo Wurmus
2020-10-26 22:50 ` Ludovic Courtès
2020-10-27 10:34 ` Ricardo Wurmus
2020-12-11 18:24 ` Giovanni Biscuolo
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=87d01gvxn8.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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 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).