From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>, 36513@debbugs.gnu.org
Subject: [bug#36513] texlive-union: Build missing font maps.
Date: Fri, 19 Jul 2019 14:04:24 +0200 [thread overview]
Message-ID: <87tvbib587.fsf@gnu.org> (raw)
In-Reply-To: <87zhlfgh4g.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 15 Jul 2019 22:47:11 +0200")
Hello,
Ricardo Wurmus <rekado@elephly.net> skribis:
> In addition to this change I just pushed to wip-texlive a number of
> changes that may lead to an even bigger number of rebuilds due to
> changes in the svn fetcher and even more TeX packages.
>
> (I noticed that the branch name “wip-texlive” was already taken by the
> attempt to add a new importer, so I just cherry-picked that commit and
> replaced the branch.)
>
> I don’t know yet if it leads to practical improvements for users, but at
> least it greatly simplifies the definition of texlive-* packages.
>
> I have yet to double check the often unclear licenses of the
> texlive-hyphen-* packages. Other than that and the WIP commit by Pierre
> at the tip I think these changes are very close to their final form.
Yay, very nice!
When it’s ready, we can ask berlin to build it as a separate branch and
merge it once it’s done.
Thanks a lot!
Ludo’.
next prev parent reply other threads:[~2019-07-19 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 15:54 [bug#36513] texlive-union: Build missing font maps Ricardo Wurmus
2019-07-15 20:31 ` Ludovic Courtès
2019-07-15 20:47 ` Ricardo Wurmus
2019-07-19 12:04 ` Ludovic Courtès [this message]
2019-07-22 19:28 ` Ricardo Wurmus
2019-07-22 20:19 ` Pierre Neidhardt
2019-07-22 21:27 ` Ricardo Wurmus
2019-09-04 13:37 ` Ludovic Courtès
2019-09-04 14:17 ` Ricardo Wurmus
2019-09-04 14:51 ` Pierre Neidhardt
2019-09-04 16:07 ` Ricardo Wurmus
2019-09-05 8:35 ` Ludovic Courtès
2020-10-17 10:07 ` bug#36513: " 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
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=87tvbib587.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36513@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--cc=rekado@elephly.net \
/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).