Revision as of 15:38, 5 January 2023

TeXLive2022

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Update the TeXLive engines and components in Fedora to the 2022 version. This will improve TeX document processing, conversion, and internationalization, which is used by some Fedora packages (and users).

Owner

Name: Tom Callaway
Email: spotrh@gmail.com

Current status

Targeted release: Fedora Linux 38
Last updated: 2023-01-05
FESCo issue: <will be assigned by the Wrangler>
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

The goal is to update Fedora to the latest available version of TeXLive (2022), including its large number of associated components.

This will resolve outstanding bugs in the existing TeXLive (2021) packages, add new features, improve performance, and expand internationalization support.

Feedback

Benefit to Fedora

Updating to TeXLive 2022 brings the latest versions of the TeX engines and components into Fedora, which improves document rendering and conversion. A number of Fedora packages include TeX support, which depend on the TeXLive utilities.

In each TeXLive release, a large (hundreds) number of TeX components are updated, a significant (~100) number of new TeX components are added, and core functionality is enhanced and optimized.

Documents should render properly and export into various formats without issues.

Scope

Proposal owners:

The necessary changes are contained to the texlive and texlive-base packages. These changes have already landed in rawhide.

Other developers:

No changes should be necessary for other packagers/developers.

Release engineering: #Releng issue number

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Objectives:

It does not align with any current Objectives.

Upgrade/compatibility impact

Users will need to delete old TexLive 2021 cache in order to properly use TeXLive 2022 upon an upgrade. To do this, a user simply (and carefully) needs to run:

rm -rf ~/.texlive2021

A new ~/.texlive2022 directory will be generated and used when the user invokes TeXLive related functionality, but TeXLive will attempt to use the older cache directory and it will not work properly.

How To Test

Packagers who have packages that use TeX to generate documentation should simply attempt to rebuild their package in rawhide with the TeXLive 2022 packages. If it succeeds and the documents generated are correct, nothing further is necessary. If it fails or the documents generated are corrupted/damaged, please open a bug against the texlive component.

User Experience

The way that the user interacts with TeX/TeXLive does not change in this release. A very small number of components (~10) in TeXLive have been obsoleted and removed, but they have either been silently replaced by other functionality or they were outdated documentation.

Dependencies

While other packages in Fedora do depend on texlive component packages, this is almost always for build-time generation of documentation, and not in a traditional "linking to library" approach.

Packages with tex() or texlive dependencies should not need to make any changes to use TeXLive 2022.

Contingency Plan

Contingency mechanism: Roll back to latest texlive/texlive-base 2021 packages.
Contingency deadline: N/A (not a System Wide Change)
Blocks release? N/A

Documentation

https://tug.org/texlive/bugs.html

Release Notes

Fedora 38 has updated its TeXLive support to 2022. Users who upgrade from older versions of Fedora and who have used TeXLive previously may need to delete the ~/.texlive2021 cache directory in order to have a working TeXLive environment. A new ~/.texlive2022 cache directory will be generated on first use of TeXLive 2022, but TeX will attempt to use older cache directories if they exist.

@@ Line 15: / Line 15: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeReadyForWrangler]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 46: / Line 46: @@
 == Benefit to Fedora ==
-<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
+Updating to TeXLive 2022 brings the latest versions of the TeX engines and components into Fedora, which improves document rendering and conversion. A number of Fedora packages include TeX support, which depend on the TeXLive utilities.
-      Be sure to include the following areas if relevant:
-      If this is a major capability update, what has changed?
-           For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
-      If this is a new functionality, what capabilities does it bring?
-           For example: This change allows package upgrades to be performed automatically and rolled-back at will.
-      Does this improve some specific package or set of packages?
-           For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
-      Does this improve specific Spins or Editions?
-           For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
-      Does this make the distribution more efficient?
-           For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
-      Is this an improvement to maintainer processes?
-           For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
-      Is this an improvement targeted as specific contributors?
-           For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
-     When a Change has multiple benefits, it's better to list them all.
+In each TeXLive release, a large (hundreds) number of TeX components are updated, a significant (~100) number of new TeX components are added, and core functionality is enhanced and optimized.
-     Consider these Change pages from previous editions as inspiration:
+Documents should render properly and export into various formats without issues.
-     https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
-     https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
-     https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
-     https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
-     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
--->
 == Scope ==
 * Proposal owners:
-<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+The necessary changes are contained to the texlive and texlive-base packages. These changes have already landed in rawhide.
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+No changes should be necessary for other packagers/developers.
 * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 93: / Line 71: @@
 * Alignment with Objectives:
 <!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
+It does not align with any current Objectives.
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
+Users will need to delete old TexLive 2021 cache in order to properly use TeXLive 2022 upon an upgrade. To do this, a user simply (and carefully) needs to run:
+rm -rf ~/.texlive2021
+A new ~/.texlive2022 directory will be generated and used when the user invokes TeXLive related functionality, but TeXLive will attempt to use the older cache directory and it will not work properly.
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 101: / Line 84: @@
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+Packagers who have packages that use TeX to generate documentation should simply attempt to rebuild their package in rawhide with the TeXLive 2022 packages. If it succeeds and the documents generated are correct, nothing further is necessary. If it fails or the documents generated are corrupted/damaged, please open a bug against the texlive component.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == User Experience ==
-<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
+The way that the user interacts with TeX/TeXLive does not change in this release. A very small number of components (~10) in TeXLive have been obsoleted and removed, but they have either been silently replaced by other functionality or they were outdated documentation.
- This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
+== Dependencies ==
+While other packages in Fedora do depend on texlive component packages, this is almost always for build-time generation of documentation, and not in a traditional "linking to library" approach.
- Describe what Users will see or notice, for example:
+Packages with tex() or texlive dependencies should not need to make any changes to use TeXLive 2022.
-  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
-  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
--->
-== Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 137: / Line 99: @@
 == Contingency Plan ==
+* Contingency mechanism: Roll back to latest texlive/texlive-base 2021 packages.
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
 * Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
+* Blocks release? N/A
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+https://tug.org/texlive/bugs.html
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
 == Release Notes ==
-<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
+Fedora 38 has updated its TeXLive support to 2022. Users who upgrade from older versions of Fedora and who have used TeXLive previously may need to delete the ~/.texlive2021 cache directory in order to have a working TeXLive environment. A new ~/.texlive2022 cache directory will be generated on first use of TeXLive 2022, but TeX will attempt to use older cache directories if they exist.
-<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
-Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
--->

Search

Changes/TeXLive2022: Difference between revisions