-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
The TinyTeX-2
bundle on macOS is too big for Github releases now
#394
Comments
Good catch ! It was sooner than we thought... We could also consider another storage option outside of Github as first discussed when migrating tinytex-releases repo. That could be worth it if the option of splitting the file require us to many hack to maintain in install scripts / function. For example, I am not sure a splitted installed file would be supported by all our installer tools like Scoop for Windows 🤔
It seems a good way. I was thinking of a manifest file with the information otherwise - file that would be ship in the release and we could read. Maybe that is what you meant by "write the number into the daily release" though |
Yes, I meant something like a manifest file.
Right. I definitely don't like hacks in several places. Currently we exceeded the limit by 20Mb. I'll first check what has introduced this extra 20Mb before deciding what to do next. |
Just tried the I'll first check if |
This reverts commit 06eb41f3806c6145a6974313622bedbdc687a8ec.
TeX Live executables optimized by Using the However, the size of the Windows bundle looks concerning. I feel it may blow up this year, so we need to take a sooner action. One solution is to use 7z a -sfx TinyTeX-2.exe $Env:APPDATA\\TinyTeX @cderv I'll leave it to you to check the size of the Assuming we switch from tinytex/tools/install-bin-windows.bat Line 36 in 142cb3e
Line 436 in 142cb3e
Line 452 in 142cb3e
|
It has exceeded the 2Gb size limit: https://github.com/rstudio/tinytex/actions/runs/3728064550/jobs/6322748726
We knew it might happen someday and here it comes... It may also happen for Windows and Ubuntu at some point.
The solution is to use
split
to split the bigtgz
file into 2Gb pieces. Then installation scripts (R, shell, choco, etc.) need to be adjusted accordingly. The tricky part is to figure out how many parts there are. Perhaps we can write the number into the daily release and read it from there. Then download the parts and extract the whole thing.The text was updated successfully, but these errors were encountered: