-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Texlive 2023 #47130
Texlive 2023 #47130
Conversation
cb45c49
to
58eab8d
Compare
58eab8d
to
ea2ccff
Compare
Small suggestion: --- a/common/build-style/texmf.sh
+++ b/common/build-style/texmf.sh
@@ -3,14 +3,11 @@ do_build() {
# Extract the source files
mkdir -p "build/usr/share/texmf-dist"
find . -maxdepth 1 -print -name "*.tar.xz" \
- -exec bsdtar -C "build/usr/share/texmf-dist" -xf {} \;
+ -exec bsdtar \
+ -s '|^texmf-dist/||' \
+ -C "build/usr/share/texmf-dist" \
+ -xf {} \;
cd "build/usr/share/texmf-dist/"
- # Everything in usr/share/texmf-dist/texmf-dist should really be in
- # usr/share/texmf-dist, so we move it
- if [ -d "texmf-dist" ] ; then
- rsync -ar texmf-dist/ ./
- rm -rf texmf-dist/
- fi
# LICENSEs are unneeded
rm -f LICENSE*
If you do this, maybe get rid of the rsync makedepends ? Do you think there's a chance we can try to fix |
Also note this: --- a/srcpkgs/texlive/patches/tlmgr.patch
+++ b/srcpkgs/texlive/patches/tlmgr.patch
@@ -63,7 +63,7 @@
+ if (!$opts{"usermode"} && $action ne "init-usertree") {
+ $opts{"usermode"} = 1;
+ print "(running on Void Linux, switching to user mode!)\n";
-+ print "(see https://docs.voidlinux.org/config/texlive.html)\n");
++ print "(see https://docs.voidlinux.org/config/texlive.html)\n";
+ }
+
# |
Thanks; applied those two. Re: texdoc, I'm not certain of the best way to attack that at this point. We can't include the docs in the main package - they're HUGE. They don't seem to be included in any tarball. This is something I'd prefer to address in a follow up PR. |
dbbfb57
to
5b8bf23
Compare
I think the docs are (optionally?) produced when each TL package is built, and placed in In spite of the name, I don't think these files TL;DR
Another note: I think texlive expects the |
Hmm, alright. I'll have a bit of a closer look at arch's texlive packages, and a couple of other distributions. Previously, the consensus was that shipping tlpdb didn't really make any sense since tlmgr system wide is unsupported. But that might not be quite true. Perhaps tlpdb should be shipped - with the intention that it is still a package managed file and is not changed by the user. (This is still something I'd prefer to address after this PR, let's get this merged first) |
5b8bf23
to
5e820b0
Compare
it seems that arch linux has dropped its collections https://archlinux.org/news/tex-live-package-reorganization/ so we may need to take them from upstream anyway. |
Testing the changes
Local build testing
A few consideration's I'm 100% sure about.texmf-dist
come from the texlive package, whereas most other distributions appear to have the primary texlive package as compiled binaries-only and then place all thetexmf-dist
binaries symlinked to scripts in their texlive-core package (obviously different names but same idea). Should we be doing this?What do I do about the ppc64 patches, should they be dropped or left?all considered now