Would be a good idea testing that before they release. Reproducible: Always
Can confirm. Wine-1.8 RC3 is out: https://www.winehq.org/announce/1.8-rc3
Hey guys, cannot you try version 9999? :)
Well wine 1.8 just got released so this is moot now.
Created attachment 420702 [details] Ebuild for wine-1.8 Ebuild is not in 1.8.x fashion, and is no longer hosted on sourceforge, therefore ebuild is updated to pull from winehq.org.
Created attachment 420704 [details] Ebuild for wine-1.8 commented-out the patches that do not apply correctly.
Wine 1.7.55 added pulseaudio support. Do we still need winepulse patches?
Created attachment 420844 [details] Ebuild for wine-1.8 Forgot to comment out the Close Paren in the PulseAudio Patches (which are no longer needed, btw). Ebuild builds without issue after this.
And now there's 1.9.0: https://www.winehq.org/announce/1.9.0 wheeeeeee \o/
(In reply to Jason Oliveira from comment #7) > Created attachment 420844 [details] > Ebuild for wine-1.8 > > Forgot to comment out the Close Paren in the PulseAudio Patches (which are > no longer needed, btw). Ebuild builds without issue after this. Without the 'run-exes' use flag, the ebuild chokes on this code segment: --- if ! use run-exes; then sed -i '/^MimeType/d' tools/wine.desktop || die #117785 fi Resulting in this: --- * Applying wine-1.5.26-winegcc.patch ... [ ok ] * Applying wine-1.4_rc2-multilib-portage.patch ... [ ok ] * Applying wine-1.6-memset-O3.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/app-emulation/wine-1.8/work/wine-1.8' ... * Running autoconf --force ... [ ok ] * Running autoheader ... [ ok ] * Running elibtoolize in: wine-1.8/ sed: can't read tools/wine.desktop: No such file or directory
(In reply to JMW from comment #9) > (In reply to Jason Oliveira from comment #7) > > Created attachment 420844 [details] > > Ebuild for wine-1.8 > > > > Forgot to comment out the Close Paren in the PulseAudio Patches (which are > > no longer needed, btw). Ebuild builds without issue after this. > > Without the 'run-exes' use flag, the ebuild chokes on this code segment: > > --- > if ! use run-exes; then > sed -i '/^MimeType/d' tools/wine.desktop || die #117785 > fi > > > Resulting in this: > --- > * Applying wine-1.5.26-winegcc.patch ... [ > ok ] > * Applying wine-1.4_rc2-multilib-portage.patch ... [ > ok ] > * Applying wine-1.6-memset-O3.patch ... [ > ok ] > * Running eautoreconf in > '/var/tmp/portage/app-emulation/wine-1.8/work/wine-1.8' ... > * Running autoconf --force ... [ > ok ] > * Running autoheader ... [ > ok ] > * Running elibtoolize in: wine-1.8/ > sed: can't read tools/wine.desktop: No such file or directory tools/wine.desktop was moved to launcher/wine.desktop it seems.
I think creating a new ebuild for recent versions of Wine takes some time. Versions 1.8 (stable) and 1.9 (development) were released on Christmas' Eve. Both may come soon, and I hope 1.8 is stable also in Gentoo.
NP-Hardass seems to have disappeared, and nobody else cares...
Resolved in 90c74adfd29572e9082a08649bb4f600fcbd38de