Hi Alexander,
That's cool - in that case what I've done is created a second package
called wine-stable which will track the stable releases of wine, and
left the 'normal' wine package to be the development one:
The stable can be found here:
https://sourceforge.net/tracker/?func=detail&aid=307
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Our stable tree version need have nothing to do with what upstream
considers stable or unstable. "stable" for our purposes entails that
the package works, and builds on a clean system, against only
dependencies that are in the stable tree. It's often