Ben Klein
Primary email: <shacklein AT SPAMFREE gmail DOT com> Wine packages email: <ben DOT klein AT SPAMFREE lamaresh DOT net>
I was the guy who built the Debian packages available at Maurilio Genovese's repository at http://lamaresh.net/. Due to long-term health problems and issues with the build scripts I wrote, I've had to hand that job over.
The Packages
Here are my recommendations for Wine packages of versions 1.2 and higher:
- One stable branch repository, one combined testing/unstable branch repository. This involves one less supported distro than what I was doing (I did testing and unstable separately).
- No patches at all should be applied to the source for released versions. This means one set of updated packages should be compiled no more frequently than once every two weeks, coinciding with new upstream versions.
- Packages for i386 should be divided into at the minimum: wine, wine-dbg and wine-dev. Any other package divisions should be for major, but optional, feature support.
Packages for amd64 should be structured like the i386 packages, but include wine64 support as separate packages. This could be a "wine" meta-package that depends on wine32, or the "wine" package being the 32bit version. The default version for amd64 must never be 64bit; wine64 must be installed separately.
- Using the Debian package names "wine" (for "stable" releases of wine) and "wine-unstable" (for development releases) should be preferred. The Ubuntu-style "wine1.2" etc. package name should never be used. In conjunction with the above recommendations, this makes the longest package name, e.g., "wine64-unstable-dbg".
I'm perfectly willing to offer my CPU time to anyone who can design an automated build system that satisfies the above recommendations. I have a quad-core Phenom with 8GB of RAM, and can compile in a ramdisk to save I/O thrashing and time. Just give me somewhere to upload the packages to when I'm done!
Anyone who would like to see my build scripts or package control files can send me an email and ask politely for them.
More random information you don't need to know
I've been using Linux systems since 2000, and Wine since about 2003. I primarily use Wine for games, but ever since testing the project out with IrfanView in 2003, I've wanted to be involved with development in some way.
My IRC nick on Freenode is man_in_shack, but I also go by man_in_ltop, man_in_irssi and a few other variations. Can someone tell me roughly how long I've been doing user support in #winehq on IRC? 
This is the first patch I had committed to Wine upstream:
commit 8df74a0edb3304dfc26bd524327f9128f63de47f
Author: Ben Klein
Date: Wed Jan 21 21:02:12 2009 +1100
winecfg: Fix a typo in autodetect_drives.I'm very proud of it 
I've since had one other patch committed.