-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
[WIP] Add wine-staging 2.0-rc1 #27551
Conversation
url "https://repos.wine-staging.com/macosx/i686/winehq-staging-#{version}.pkg" | ||
name 'Wine-staging' | ||
homepage 'https://www.wine-staging.com/' | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add the line depends_on cask: 'xquartz'
- see here.
name 'Wine-staging' | ||
homepage 'https://www.wine-staging.com/' | ||
|
||
pkg "wine-staging--#{version}.pkg" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be pkg "winehq-staging-#{version}.pkg"
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It now reports success install, but I can't run it, e.g.
LC_ALL=C wine
-bash: wine: command not found
``
The
|
fixes according to miccal.
@miccal thanx for your help. |
Does this need Wine to be installed also? If so, you will also need to add the line |
Wine-Staging is a bleeding-edge test branch of wine, it contains wine binary itself. |
Does it work if you install the |
Yes, but In this case I don't see any mention of "winehq" in |
But you can run it when you install it manually? Do you have Xquartz installed? |
@miccal yes, but it doesn't use it. |
I installed this via
Running the suggested command
However, if I open a new Terminal window and enter the same command I get Like yourself, I don't see any mention of "winehq" in In conclusion, I would say that the Cask installs successfully. I hope all this helps. |
'org.winehq.wine-staging-deps64', | ||
'org.winehq.wine-staging32', | ||
'org.winehq.wine-staging64', | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add delete: "#{appdir}/Wine Staging.app"
to the uninstall
stanza.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this not uninstalled using pkgutil
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No - when I ran brew cask uninstall https://raw.githubusercontent.com/yurikoles/homebrew-cask/8f0463f8c16148e482cc04c7720f4e338d54bec8/Casks/wine-staging.rb
it did not remove the app.
I did think that was weird, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, thats why I dont commit my wine-staging cask. Seems all those pkg dont appear in pkgutil --pkgs|grep wine
after installing the pkg, though the pkg really include the 5 sub-pkg with the name mentioned above.
This is because Wine Staging.app adds the
If you add |
Thanks for that @numbermaniac. As @palxex mentioned, the 5 packages do not appear in Ping @caskroom/maintainers - should we add this Cask? |
I have no issue with the |
Whoops, thanks @vitorgalvao. |
@yurikoles, can you confirm this is working now? |
@@ -0,0 +1,21 @@ | |||
cask 'wine-staging' do | |||
version '1.9.23' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this cask was created, the latest version has now become 2.0-rc1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming the rc1
refers to Release Candidate 1, I think we will keep it at he latest "stable" version for now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not correct, since whole 1.9-branch is considered as development version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated to 2.0-rc1.
Also, does this enable the 64-bit Wine option that is offered when installing manually? |
@yurikoles can you confirm this? I do not have my testing machine available at the moment. |
@miccal it doesn't install 64-bit version now. |
Thanks @adidalal but I was under the impression that this does not allow the user to actually make a choice? |
No, I don't believe so - that wasn't the intention of the feature, though, more so to allow for "optional" components to be auto-selected and installed so that we can move away from |
IMO 64-bit should just be enabled for everyone, there isn't much of a reason why you wouldn't want it. |
Closed in favour of #27937. |
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:
brew cask audit --download {{cask_file}}
is error-free.brew cask style --fix {{cask_file}}
reports no offenses.Additionally, if adding a new cask:
brew cask install {{cask_file}}
worked successfully.brew cask uninstall {{cask_file}}
worked successfully.I have problem with cask, install ends with message
Error: pkg source file not found: '/usr/local/Caskroom/wine-staging/1.9.23/wine-staging--1.9.23.pkg'
Full logs here: https://gist.github.com/yurikoles/fd1f99586a46d41d654d62510de9bb78