-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
winePackages.fonts: init at 4.0 #63044
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
Conversation
"Wine's fonts should be a natural candidate for their own subpackage" https://wiki.winehq.org/Packaging They are a replacement for some Microsoft fonts not available in other replacement packages.
Does the normal build of Wine also build the fonts? Should they just be an extra output? |
The fonts are included in the source and don't need building. |
Are |
Yes, I think so, except for Wine. |
I think it is possible to have a |
But then someone wanting to use just the fonts has to build wine, even if the fonts are just copied from the source. (Which takes a long time) |
This pull request has been mentioned on Nix community. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/20 |
The overhead of performing two separate builds instead of one with an output seems to be quite small here. Considering one build is much faster compared to the other, I think it is fine to have them separated. |
Motivation for this change
https://wiki.winehq.org/Packaging
They are a replacement for some Microsoft fonts not available in other
replacement packages, e.g. Tahoma.
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)