Skip to content
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

Closed
wants to merge 6 commits into from
Closed

[WIP] Add wine-staging 2.0-rc1 #27551

wants to merge 6 commits into from

Conversation

yurikoles
Copy link
Contributor

@yurikoles yurikoles commented Dec 9, 2016

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.
  • The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

  • Named the cask according to the [token reference].
  • brew cask install {{cask_file}} worked successfully.
  • brew cask uninstall {{cask_file}} worked successfully.
  • Checked there are no [open pull requests] for the same cask.
  • Checked that the cask was not already refused in [closed issues].

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

@yurikoles yurikoles changed the title add wine-staging 1.9.23 [WIP]add wine-staging 1.9.23 Dec 9, 2016
url "https://repos.wine-staging.com/macosx/i686/winehq-staging-#{version}.pkg"
name 'Wine-staging'
homepage 'https://www.wine-staging.com/'

Copy link
Contributor

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"
Copy link
Contributor

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".

Copy link
Contributor Author

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
``

@miccal
Copy link
Contributor

miccal commented Dec 9, 2016

The pkg stanza requires an uninstall. Please add the following:

  uninstall pkgutil: [
                       'org.winehq.wine-staging',
                       'org.winehq.wine-staging-deps',
                       'org.winehq.wine-staging-deps64',
                       'org.winehq.wine-staging32',
                       'org.winehq.wine-staging64',
                     ]

fixes according to miccal.
@yurikoles
Copy link
Contributor Author

yurikoles commented Dec 9, 2016

@miccal thanx for your help.
Up & rebase. But still can't run it.

@miccal
Copy link
Contributor

miccal commented Dec 9, 2016

Does this need Wine to be installed also? If so, you will also need to add the line depends_on formula: 'wine'.

@yurikoles
Copy link
Contributor Author

Wine-Staging is a bleeding-edge test branch of wine, it contains wine binary itself.

@miccal
Copy link
Contributor

miccal commented Dec 9, 2016

Does it work if you install the pkg manually?

@yurikoles
Copy link
Contributor Author

yurikoles commented Dec 9, 2016

Yes, but In this case I don't see any mention of "winehq" in pkgutil --pkgs. I don't see it either by installing the cask.

@miccal
Copy link
Contributor

miccal commented Dec 10, 2016

But you can run it when you install it manually? Do you have Xquartz installed?

@yurikoles
Copy link
Contributor Author

@miccal yes, but it doesn't use it.

@miccal
Copy link
Contributor

miccal commented Dec 10, 2016

I installed this via brew cask install https://raw.githubusercontent.com/yurikoles/homebrew-cask/8f0463f8c16148e482cc04c7720f4e338d54bec8/Casks/wine-staging.rb on a machine running macOS 10.12.1 and Xquartz 2.7.11. It created an .app called Wine Staging.app, which when I run opens a Terminal window with the following output:

################################################################################
#                           Wine Is Not an Emulator                            #
################################################################################

 Welcome to wine-1.9.23 (Staging).

 In order to start a program:
   .exe: wine program.exe
   .msi: wine msiexec /i program.msi

 If you want to configure wine:
   winecfg

 To get information about app compatibility:
   appdb Program Name

-bash-4.4.5- /Users/USER [> 

Running the suggested command wine --check-libs results in the output:

libcups.2.dylib: /usr/lib/libcups.2.dylib
libfreetype.6.dylib: /opt/x11/lib/libfreetype.6.dylib
libGL.1.dylib: /opt/x11/lib/libGL.1.dylib
libjpeg.62.dylib: /Applications/Wine Staging.app/Contents/Resources/wine/lib/libjpeg.62.dylib
libncurses.5.4.dylib: /usr/lib/libncurses.5.4.dylib
libnetapi.dylib: missing
libodbc.dylib: missing
libOSMesa.8.dylib: /opt/x11/lib/libOSMesa.8.dylib
libpcap.A.dylib: /usr/lib/libpcap.A.dylib
libpng15.15.dylib: /opt/x11/lib/libpng15.15.dylib
libtiff.5.dylib: /Applications/Wine Staging.app/Contents/Resources/wine/lib/libtiff.5.dylib
libtxc_dxtn.dylib: /Applications/Wine Staging.app/Contents/Resources/wine/lib/libtxc_dxtn.dylib
libX11.6.dylib: /opt/x11/lib/libX11.6.dylib
libX11-xcb.1.dylib: /opt/x11/lib/libX11-xcb.1.dylib
libXcomposite.1.dylib: /opt/x11/lib/libXcomposite.1.dylib
libXcursor.1.dylib: /opt/x11/lib/libXcursor.1.dylib
libXext.6.dylib: /opt/x11/lib/libXext.6.dylib
libXi.6.dylib: /opt/x11/lib/libXi.6.dylib
libXinerama.1.dylib: /opt/x11/lib/libXinerama.1.dylib
libXrandr.2.dylib: /opt/x11/lib/libXrandr.2.dylib
libXrender.1.dylib: /opt/x11/lib/libXrender.1.dylib
libxslt.1.dylib: /usr/lib/libxslt.1.dylib
libXxf86vm.1.dylib: /opt/x11/lib/libXxf86vm.1.dylib

However, if I open a new Terminal window and enter the same command I get -bash: wine: command not found as you did. So it seems that you MUST run the app Wine Staging.app and use the Terminal window that it opens.

Like yourself, I don't see any mention of "winehq" in pkgutil --pkgs.

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',
]
Copy link
Contributor

@miccal miccal Dec 10, 2016

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.

Copy link
Member

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?

Copy link
Contributor

@miccal miccal Dec 10, 2016

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.

Copy link

@palxex palxex Dec 10, 2016

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.

@miccal miccal added the awaiting user reply Issue needs response from a user. label Dec 10, 2016
@numbermaniac
Copy link
Contributor

numbermaniac commented Dec 15, 2016

However, if I open a new Terminal window and enter the same command I get -bash: wine: command not found as you did. So it seems that you MUST run the app Wine Staging.app and use the Terminal window that it opens.

This is because Wine Staging.app adds the wine binary to the path first when it opens Terminal. If you scroll up in the Terminal window, this is the code it runs first:

test "$?BASH_VERSION" = "0" || eval 'setenv() { export "$1=$2"; }'; setenv PATH "/Applications/Wine Staging.app/Contents/Resources/start/bin:/Applications/Wine Staging.app/Contents/Resources/wine/bin:$PATH"; winehelp --clear

If you add "/Applications/Wine Staging.app/Contents/Resources/start/bin:/Applications/Wine Staging.app/Contents/Resources/wine/bin:$PATH" to your path in .bash_source, then wine will always be available when you open a Terminal.

@miccal
Copy link
Contributor

miccal commented Dec 15, 2016

Thanks for that @numbermaniac.

As @palxex mentioned, the 5 packages do not appear in pkgutil --pkgs which then affects the uninstall as pointed out by @reitermarkus.

Ping @caskroom/maintainers - should we add this Cask?

@miccal miccal added the awaiting maintainer feedback Issue needs response from a maintainer. label Dec 15, 2016
@vitorgalvao
Copy link
Contributor

I have no issue with the app having to be deleted separately. It seems to be fairly common in pkg casks, as for some reason many times they are left behind (sometimes even just an empty app bundle). If it leaves many other things behind, that's another matter.

I have no strong feelings one way or the other.

@miccal miccal removed the awaiting user reply Issue needs response from a user. label Dec 15, 2016
@miccal
Copy link
Contributor

miccal commented Dec 16, 2016

Whoops, thanks @vitorgalvao.

@reitermarkus reitermarkus removed the awaiting maintainer feedback Issue needs response from a maintainer. label Dec 16, 2016
@reitermarkus
Copy link
Member

@yurikoles, can you confirm this is working now?

@reitermarkus reitermarkus added the awaiting user reply Issue needs response from a user. label Dec 16, 2016
@@ -0,0 +1,21 @@
cask 'wine-staging' do
version '1.9.23'
Copy link
Contributor

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.

Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor

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.

@numbermaniac
Copy link
Contributor

Also, does this enable the 64-bit Wine option that is offered when installing manually?

@miccal
Copy link
Contributor

miccal commented Dec 17, 2016

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.

@yurikoles
Copy link
Contributor Author

@miccal it doesn't install 64-bit version now.

@miccal
Copy link
Contributor

miccal commented Dec 17, 2016

Installing the pkg manually, you are presented with the following:

screen shot 2016-12-17 at 7 29 31 pm

I am not sure how to select that option as a user choice via Cask.

@miccal miccal removed the awaiting user reply Issue needs response from a user. label Dec 17, 2016
@miccal miccal changed the title [WIP]add wine-staging 1.9.23 [WIP] Add wine-staging 2.0-rc1 Dec 17, 2016
@miccal
Copy link
Contributor

miccal commented Dec 18, 2016

Thanks @adidalal but I was under the impression that this does not allow the user to actually make a choice?

@adidalal
Copy link
Contributor

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 installer :manual

@numbermaniac
Copy link
Contributor

IMO 64-bit should just be enabled for everyone, there isn't much of a reason why you wouldn't want it.

@miccal miccal mentioned this pull request Dec 18, 2016
8 tasks
@miccal
Copy link
Contributor

miccal commented Dec 18, 2016

Closed in favour of #27937.

@miccal miccal closed this Dec 18, 2016
@Homebrew Homebrew locked and limited conversation to collaborators May 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants