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
Provide and use 'tex' virtual package #23559
Conversation
Don't worry about CI, CI doesn't like TeXLive's distfile, something about FTP I think Looks fine to me. |
[ci skip]
I've CI is going to fail anyway, I'll just pull everything in one pass. I added the xournalpp and lyx updates and am now testing locally. |
Hm, this isn't bad per se, but I think texlive metapackages should be the providers, and make texlive-most the default provider. To be fair, texlive does pull in texlive-core, so this does yield a working installation, but it will only work for the most basic tex documents. Thoughts? |
The
texlive
virtual package has been renamedtex
to be more generic and avoid confusion with the new "native"texlive
package, andtexlive
has been named the default provider for the new virtual.Every
texlive*-bin
package providestex
with a version based on its own (which is the release year); the newtexlive
strips the month and day from its year to similarly providetex
with a version by year.A few texlive dependents that are quick to build have been updated to depend on the new virtual, and I've bumped
python3-pyx
while I was at it.This is really motivated by
xournalpp
, which is ready to go with the new virtual, but I'm holding back because I want this to run through CI and I'm afraidxournalpp
will time out.This will also break
lyx
which currently depends onvirtual?texlive
, but that's also ready to go with a new version bump. Again, includinglyx
here might overrun Travis time limits.Seeking comments from @q66 and @fosslinux since they shepherded the new
texlive
as well as @leahneukirchen astexlive*-bin
maintainer.