Open GoogleCodeExporter opened 8 years ago
...and new Debian package wine-Unstable showed:
joerg [9]:~$ dpkg -l wine-unstable
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-======================-================-================-===================
==============================
ii wine-unstable 1.7.18-1 amd64 Windows API
implementation - standard suite
joerg [10]:~$ wine-unstable --version
wine-1.7.18-1615-gff569f2
Original comment by Joerg.Schiermeier@gmail.com
on 7 May 2014 at 7:42
IMHO we should definitely handle those kinds of version numbers, they're
fairly common. (I mean, we could yell at the distro maintainers, but that's
not likely to be productive.)
I'll try to put the fix together.
Original comment by daniel.r...@gmail.com
on 7 May 2014 at 7:56
Also the executabel in Debian changed to wine-unstable so the actuacl version
of wine didn't interfere with stable wine. The unstable wine executable is
named: wine-unstable.
Here is some code I use to get the version number:
test -x '/usr/bin/wine-unstable' && \
WINE32_BIN="/usr/bin/wine-unstable"
test -x ${WINE32_BIN} && WINE_VER=$(${WINE32_BIN} --version | \
sed -e 's/^.*\([0-9]\{1\}\.[0-9]\{1,2\}\.[0-9]\{1,3\}\).*$/\1/')
Hopefully this will help.
Thanks for your attention
Joerg
Original comment by Joerg.Schiermeier@gmail.com
on 7 May 2014 at 9:11
Original issue reported on code.google.com by
Joerg.Schiermeier@gmail.com
on 4 May 2014 at 8:56