Skip to content
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

Merged
merged 13 commits into from Jul 14, 2020
Merged

Conversation

ahesford
Copy link
Member

The texlive virtual package has been renamed tex to be more generic and avoid confusion with the new "native" texlive package, and texlive has been named the default provider for the new virtual.

Every texlive*-bin package provides tex with a version based on its own (which is the release year); the new texlive strips the month and day from its year to similarly provide tex 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 afraid xournalpp will time out.

This will also break lyx which currently depends on virtual?texlive, but that's also ready to go with a new version bump. Again, including lyx here might overrun Travis time limits.

Seeking comments from @q66 and @fosslinux since they shepherded the new texlive as well as @leahneukirchen as texlive*-bin maintainer.

@fosslinux
Copy link
Contributor

Don't worry about CI, CI doesn't like TeXLive's distfile, something about FTP I think

Looks fine to me.

@ahesford
Copy link
Member Author

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.

@ahesford ahesford merged commit 648d023 into void-linux:master Jul 14, 2020
@ahesford ahesford deleted the tex-virtual branch July 14, 2020 19:54
@fosslinux
Copy link
Contributor

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?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants