@kjharcombe Hey Keiran, how's it going? We have seen your mail on the TL mailing list, so we wonder if you want to focus on that for now? :)
8 replies
What was the name of the band that did the Zelda's cover music of Paulo Cereda's presentation at TUG 2021? 🎶 🙂
1 reply
Just heard about the Island of TeX BTW, really cool project!
7 replies
For example I think the official or semi-official container images of TeX Live was a true need! Thanks for that!
1 reply
Oh, and for everyone coming here after Paulo's talk today: We missed to mention https://gitlab.com/islandoftex/archive which provides an archive of older (abandoned) TeX-related projects (hosted on SourceForge or other hosters where it is unclear whether old source code is well preserved). If there are any ideas what's missing, simply reach out to us 🙂
By the way, just for the sake of my curiosity, do you mind if I ask why you chose Kotlin?
3 replies
We can program with COBOL and as long as we are having fun, let's go! 😉
1 reply
oh no
Interesting, I thought Kotlin was more on the mobile side of things but it seems I should have a closer look 😄
2 replies
Kotlin in data science is now a reality. :)
hmenke: welcome :)
Paulo Cereda: While I'm here: Any chance we are going to see native Arara binaries at some point? Kotlin supports building native code: https://kotlinlang.org/docs/mpp-build-native-binaries.html
2 replies
But since I don't speak Kotlin myself, I don't know what kinds of caveats are involved there.
I already had the feeling that it wouldn't be that easy. Thanks for looking into it.
What's the size of the IoT TeX Live Docker images? I'm considering using them for CI, but I'm also a little bit concerned about bandwidth, because on those systems unused images are pruned nightly.
1 reply
Ideally you wouldn't install all of TeX Live into a single layer as you are doing right now. The perfect layering would install packages with a similar update frequency in upper layers and base packages in lower layers.
1 reply
Maybe you will find this interesting: https://grahamc.com/blog/nix-and-layered-docker-images
1 reply
Unfortunately, TeX Live's dependency management is suboptimal, to say it politely, so applying this technique will be non-trivial.
Putting weekly updates in their own layer should work out. There is an upper limit of 125 layers (or so) in a Docker image, but since TeX Live releases only live for a year there can be at most 52 weekly updates.
Hi Paulo!
I've just updated arara on TeX Live and noticed a difference. Currently TL has bib2gls v2.7, but I have bib2gls aliased to my local copy (2.8). Previously arara was using my development version (from the alias) but now its using the TL version.
I'm not sure if maybe I also installed TL bib2gls when I was updating arara.
IIRC the execution thingy refers to the first match in a path lookup. Maybe TL bib2gls was indeed updated and the TL path might be first, it was selected...
How was bib2gls 2.8 referenced? As an alias?
I don't know if aliases would work in a subprocess...
Yes, it's aliased in my
.bashrc as alias bib2gls=$HOME/programming/java/bib2gls/src/bin/bib2gls
I'll try added a symlink in
~/bin instead of an alias. That directory comes before TL's bin
What does
which -a bib2gls give?
Don't know why it worked before but then stopped working
alias bib2gls='/home/nlct/programming/java/bib2gls/src/bin/bib2gls'
~/programming/java/bib2gls/src/bin/bib2gls
~/bin/bib2gls
/usr/local/texlive/default/bin/x86_64-linux/bib2gls
~/bin/bib2gls
/usr/local/texlive/default/bin/x86_64-linux/bib2gls
~/bin/bib2gls
Oh it's missing the first line