Title says it all, really. I've been in the practice of taking the latest wine source and the build script from slackbuilds.org and building my own package from that. However, now there are premade slackware packages direct from wine's sourceforge with the latest development release of wine. That would certainly be easier.

Does anyone have strong opinions on building your own wine or just using their packages, and why?

Thanks—
—quiescere

I do not use wine, but generally speaking I would use a premade package only if:
(1) I trust the packager
and
(2) the SlackBuild is available so I can check it.

I run a modified wine.slackbuild based on the one from Slackbuilds.org and my own script before SBo had a WINE slackbuild. I do this to be able to tweak functionalility under a x86_64 multilib environment. I don't use the packages from winehq sourceforge.

Besides, its easy enough to compile. Just takes a bit of time.

In the past I've used the slackbuilds to build packages from newer source available from winehq without any problems.


I'm also a really big fan of the guys at Codeweavers who offer the crossover games program, essentially a precompiled closed source wine and assorted helper tools. Very handy!

As a rule, I usually check to see if AlienBob has a version of anything funky. If so, that's what I use. This is one of those cases.

Up to somewhere around version 1.2 I usually compiled wine myself and installed it under /usr/local. Since then I got lazy and I've used the packages provided by the wine project. Although coming back to Slackware since version 9.0, I only learned about slackbuild.org nearly two years ago (shame on me). Since I've never had any problems with the prebuild packages from the wine-project, I still use those on my 64bit-multilib system. For other projects, I now use the SBO-scripts if available.
By the way, the slackbuild-script used is included in the package and based on version 1.1.29 of Eric's script.

Wine is a pretty straightforward compile, so I compile it. If it required changing settings and stuff, I might use someone else's. But seeing that it usually has no compiling hiccups, I just make it myself.

I use wine 1.3 from Wine as it runs the only game I play on better than any other version, including newer ones. I have no strong feelings though about using Wine's, Alien_Bob's or a Slackbuild - I'll use what works best. I wouldn't take one off the web from a random site I didn't have some knowledge of though. I've compiled it in the past too - I like compiling my own stuff - often it's the best way to get the most up-to-date version (though it may not stay that way of course).

Did you manage to compile the latest version? On my 64+multilib I can compile Wine 1.5.6 and 1.5.13 (it's the latest version on SBo), but today I've tried 1.5.24 without success. Not sure if it's a multilib problem or something else.

Hi elesmod,

I was able to compile wine-1.5.24 successfully. I used a slightly modified version of this script:

http://bender.open-source.co.uk/~tad...ate.SlackBuild

The script wasn't created by me obviously, but it should still work fine for compiling wine-1.5.24 (and my modified script did compile it). What I basically modified was the configure lines to match those within the wine.SlackBuild provided by Simone Giusetti (who uploads the final package on winehq.org) and something in the bottom half of the script as well (can't remember, it might be a man page compression thing or something).

Just tried 1.5.24 and 1.5.25 and looks like we have got this clang goofyness going on: http://bugs.winehq.org/show_bug.cgi?id=32872

The Wine-1.2.24 Slackbuild from Simone Giustetti (http://www.winehq.org/download) is a modified version of Alien Bob's script, and seems to work, but I can't seem to figure out how he isn't bothered by the error. Other that building win64, there is no significant difference.

I use SBo's SlackBuild to build the stable version of Wine (currently 1.4.1).