top-level: build winePackages on Hydra #40620
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good! One thing I’ve been wanting to do is move winePackages to top-level/wine-packages.nix. Does that make sense to do in this pr? |
lukateras
force-pushed
the
yegortimoshenko-patch-4
branch
from
af719fd
to
1b2b126
Compare
|
Sure, done. |
matthewbauer
approved these changes
May 17, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use case: I would like to work around https://bugs.winehq.org/show_bug.cgi?id=41930, and that requires Wine build with
openglSupport = false;. That currently means I have to build Wine. It would be neat to be able to usewinePackages.minimalfrom cache.The same concern largely applies to
wineUnstable, which is the latest development release of Wine without experimental staging patches on top of it. Staging breaks many apps (which is why those patches aren't merged upstream), but some crucial fix might have been merged recently and is not in stable yet. (This, for example, applies to The Sims 4).