-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add font patcher in release #484
Comments
It would be great to have some kind of option to cherry-pick only parts of this repository, or a separate |
i wanted that too and realy didnt feel like downloading 2GB just for the patcher. |
Hey @ryanoasis, could we get your thoughts on this? Got a few folks in the NixOS community rooting for this ^_^ |
Things are going to be changing. Patcher and it's required files are going to live in a separate repo. Putting the patcher in the release is still an interesting idea. Releases are one of my main focuses ATM since they are a PITA and really slowing everything down. Have made progress but nothing public yet. |
I've for the moment done a 180º upon more consideration, I think now that having the font patcher part of the release solves most/all problems as it'll come bundled with the necessary files. Also moving to a separate repo seems like it'll only cause maintenance issues without providing much benefit. Open to more discussion: #716 for |
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference. |
Currently the releases do not contain the font patcher. The only way to download the patcher and its fonts is to manually download, or to use some obscure feature of git or svn to download the individual folder of the patcher. Can this be made into a release?
The text was updated successfully, but these errors were encountered: