-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Minor modifications to make a better tutorial #24
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Leave a comment to keep the issue open, explaining why. |
jajaja |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
I'm guessing you mean that texliveonfly won't detect these ones? How did you find this list? I don't have them here yet: https://tex.stackexchange.com/a/463842/98850 (under 'known problems')
To create the package list you can use the following trick
```bash
pdflatex -draftmode -interaction=batchmode "\RequirePackage{snapshot}\input{main}" &&
perl -wnE 'say $1 if /(?:\*\{p.+?\}\s*)\{(.+?)\}(?:\s*\{.+?\})/' snapshot.dep
```
|
@pablgonz Ah I see you used the snapshot package, didn't know that one existed. But the snapshot.dep file shows LaTeX packages, not TeX Live packages, so it's not perfect (and you have to have all packages installed locally before it works) - though it definitely helps figuring out dependencies :) |
I really don't think you can have a definitive solution to create the list of necessary packages, the after_script:
- export PATH=/tmp/texlive/bin/x86_64-linux:$PATH
- tlmgr list --only-installed | grep -oP 'i \K.+?(?=:)'
name: "Run texlive-test" Update my fork to your repository and I added some small changes, give me your opinion and if this correct I will do a pull request. |
LaTeX tools will never be perfect, but we try to get as close as we can 😄 That will be useful, but I would prefer it if we do that the other way around, first you make a pull request and then I can approve the changes ;) Good one, forgot about that. I think they didn't even have that custom build feature yet when I started using Travis. I just put a note for that in the Troubleshooting section. |
Just consider the last commit, Modifications are for
TeXLive
only:travis.yml
.texlive-test
for minted and biber.main.tex
file to compile without errors.sudo apt-get install python-pygments
to filetravis.yml
.dist: xenian
to the filetravis.yml
.I think that's all, in my tests compile everything without problems.
Greetings