Texlive 2025
- I tested the changes in this PR: yes. I can compile latex documents just fine, and all tests pass in chroot.
- built natively for
aarch64-glibc,x86_64-glibc - cross compiled for
x86_64-glibc texlive-core: adapt helpers from Alpine Linux to process collectionstexlive: removetlmgras everything is packaged viaxbps, and splitlatexindentsubpkg.- fixed the use of
texdoc
cc: @fosslinux @tornaria @leahneukirchen
To do: patch for moving latexmk into base, (?) do not split latexindent.
To do for collections: split configuration files (e.g. Debian moves them to TEXMFSYSCONFIG=/etc/texmf) and adapt our trigger:
- updmap config files:
updmap.d - hyphenation-related config files (language.def and language.dat fragments):
language.d - fmtutil config files:
fmt.d,fmtutil
To do: fix conflicts
texlive and texlive-LuaTeX conflict for
/usr/bin/lualatex
/usr/bin/optex
texlive and texlive-XeTeX conflict for
/usr/bin/xelatex
texlive-LuaTeX and texlive-dvi conflict for
/usr/bin/dvilualatex
/usr/bin/dviluatex
Probably fine, but I don't use this package.
is this something to worry about?
Updating texmf-dist formats...
(guessed encoding #4: ASCII = utf8)
If it still succeeds, I don't think so, the upsteam TeXLive prints the same.
Yes, it succeeds. Thanks!
Fixed and simplified cross-compiling.
One nitpick: how do I edit (in configure) --with-banner-add=/VoidLinux, such that it adds a space in between?
@tornaria I think I fixed texdoc, in case you want to try this (e.g., texdoc enumitem opens the pdf :)
Any status update on this? This looks fairly good to me.
@dkwo if you would like to take Maintainer= of TeXLive as well, be my guest:)
This has been working fine for me all this time.
It would be nice to use either svn or git for the distfiles, since they contain point releases (of the form 2025.2) with some small updates, but the first uses svn and the second does not seem to provide tarball archives. Maybe sometimes in the future?
Also, texlive-core is quite large: is it acceptable to keep it like this? or should I at least split a docs subpkg?
I think I found a way to adapt the Alpine Linux script for packaging collections, which gives a better result in terms of size. I will push a sample for comments and review, before I add all collections, as we may want to move the helper functions somewhere else.
I had to add collection dependencies the dumb way by hand, as the inject script does not work as is (they are also not correct in current Void repo). I still have to split the docs subpackages, as they are huge.
I may need some help fixing the fmtutil trigger, now that languages are split. The problem is that they provide a single file with everything, while we would need per language.
Packaging collections has the extra complication of dealing with hyphenation, fmt and similar files, which are now split. For now, I go back to one single package, and just split the docs. I also resolved the conflicts in texlive. Once we find a proper way to deal with collections (e.g. using Alpine's functions, which however still requires a way to deal with those files), we can go back to split collections if we want.
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.
This is ready to review, I have been using it for a while. @leahneukirchen Now that arXiv is also on texlive 2025, it may be a good time to update. @fosslinux I partially took your offer, and added myself to the maintainers string.