From: Ricardo Wurmus <rekado@elephly.net>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 42449@debbugs.gnu.org
Subject: bug#42449: texlive: l3regex.sty not shipped with texlive-latex-l3kernel
Date: Tue, 21 Jul 2020 13:52:19 +0200 [thread overview]
Message-ID: <87k0yxytjg.fsf@elephly.net> (raw)
In-Reply-To: <53467e62-1ca5-e552-2982-42ca7bab96bf@web.de>
Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:
> On 21.07.20 12:07, Ricardo Wurmus wrote: > Thanks for the report. Yes,
> the “texlive-latex-l3kernel” package is
>> incomplete. Most of the packages whose names follow the
>> “texlive-{latex,tex,generic}-*” pattern are incomplete because they
>> predate the introduction of “texlive-origin” (and more importantly
>> “svn-multi-fetch”).
>>
>> For all of these packages we need to write replacements that include all
>> source files as listed in $(guix build texlive-bin)/share/tlpkg/texlive.tlpdb
>
> Oke, I understand. So do we have examples of completely working texlive
> packages where I can have a look and try to do the same for l3kernel?
Yes. Examples include “texlive-charter” (to replace
“texlive-fonts-charter”), “texlive-xypic” (to replace
“texlive-fonts-xypic” and “texlive-generic-xypic”), “texlive-xcolor”
(replacing “texlive-latex-xcolor”), etc.
Search for deprecated-package in tex.scm and you should find more
examples.
--
Ricardo
prev parent reply other threads:[~2020-07-21 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 21:22 bug#42449: texlive: l3regex.sty not shipped with texlive-latex-l3kernel Jonathan Brielmaier
2020-07-21 10:07 ` Ricardo Wurmus
2020-07-21 10:29 ` Jonathan Brielmaier
2020-07-21 11:52 ` Ricardo Wurmus [this message]
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=87k0yxytjg.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=42449@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
/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).