From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>,
arm@gentoo.org, hppa@gentoo.org, tex@gentoo.org
Subject: [gentoo-dev-announce] TeX Live 2023 stabilization imminent
Date: Sun, 9 Jun 2024 19:00:34 +0200 [thread overview]
Message-ID: <dc7a2b12-3cc7-4181-8666-7fbd82ca9971@gentoo.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1264 bytes --]
After many months of work, the stabilization of TeX Live 2023 is imminent.
I would first like to thank everyone who contributed, reported bugs, and
helped to make this happen. Special thanks goes to negril for providing
the initial prototype ebuilds that helped to get this going.
TeX Live 2023 got a major overhaul and new tooling. User-facing
highlights include
- all binlinks and binscripts are now properly installed and in PATH
- all manpages are now installed (due to upstream's design, only if USE=doc)
- tlmgr is now available (but forced into user mode, as done by other
distributions)
- the tlpdb is dynamically created, texdoc works (if USE=doc)
While I do not have any reason to believe that there are remaining
issues lurking in TeX Live 2023, I would like to use this as opportunity
to encourage advanced users to switch to TeX Live 2023 right now. Please
report issues that come up.
The re-keywording of TeX Live 2023 is ongoing in
https://bugs.gentoo.org/932752.
Unfortunately two stable arches are lacking: arm and hppa. It would be
great If the respective arch teams could prioritize the keywording.
Otherwise, the arches may missing out on the upcoming stabilization request.
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17797 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
reply other threads:[~2024-06-09 17:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=dc7a2b12-3cc7-4181-8666-7fbd82ca9971@gentoo.org \
--to=flow@gentoo.org \
--cc=arm@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hppa@gentoo.org \
--cc=tex@gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox