Installing Wine on Slackware 13.0
 

I'm back to slack after several years.
I'd like to install wine.
I have downloaded wine-1.1.33.tar.bz2
from http://sourceforge.net/projects/wine...re%20Packages/
I am currently looking at the installation instructions.

I would welcome any advice, comments or caveats that might
contribute to the installation. In particular, have I made the
correct download?

Another example: My preference is that the installation be made to
/usr/local, since that directory is on its own partition.
Will that introduce any problems?

thanks
tim

I can't answer your partition question right, but coincidentally ... I'm compiling v1.1.37 right now using the slackbuilds.org script (obviously with the 1 line modified for the new version number). I installed it a couple of days ago (last time I tried Wine was a couple of years ago) - and I'm very impressed.

Although I'm new to Wine, the latest version (to me) does not seem any less stable than the earlier versions, although I did make the mistake to not install Gecko at first, so I had no clue why HTML content was not loading. (Whoops)

The slackbuilds.org script, along with the official dev download from winehq seem to work well with each other.

I'm interested to see what initial success (or failures) you have from the sourceforge slack packages installation.

I think you have opened a whole new can of worms - or bottle of wine!
What you have provided is probably a better path for me to pursue.
It is late here, so I will investigate the link to slackbuilds.

Two questions now:
How do I install gecko on slack?
Also, after some investigation, I see that line 4 in wine.info of slackbuild package
should be changed to the URI: http://ibiblio.org/pub/linux/system/...1.1.37.tar.bz2
I believe that the m5sum value needs to be changed also, but as I write,
can't find it.

Thanks very much.
tim

To get round the md5sum bit either download Alien Bob's slackbuild (it doesn't take the md5sum into account), or if you are using the slackbuilds.org script just do a md5sum on the file and copy the result into the info file.

You do not say which version of Slackware you are running, if you are running Slackware64-13.0 you will need Alien Bob's compatibility layer installed or you will not be able to cross-compile wine.

samac

I knew I'd seen this recently. From dugan's site http://www.vcn.bc.ca/~dugan/setting-up-slackware.html samac

just for LOLs: this can be seen as another step in automation for executing windows worms. :D

Sorry.
Slackware 13.0 - 32-bit
And where is the URL for Alien Bob's slackbuild.
I'd like to have a look at it also.
thanks

http://connie.slackware.com/~alien/s...ds/wine/build/ You will have to edit the version number.

samac

Hey, I like that. Looks like it might do everything right there.
As to the version number, am I correct that one would edit the
string at line number 96 to or whatever is the target version?

Another observation I make is that /usr is hard-coded.
If /usr were edited to /usr/local would we not have
an installation under /usr/local? Or better yet, something like a
$dst variable which could in one edit control the destination
of installation?

To clarify, I made my installation to 3 partitions
1)/home
2)/ (root)
3)/usr/local

That should enable me to make a slackware upgrade without having to
re-install applications not included in the stock slack installation.
Of course, certain system - wide configurations might have to be made.

Or would I be opening another can of worms here?
I'd welcome the opinions of those wiser than I:twocents:

The version number thing is correct. If you go down to the configure section of the script there is a line edit that to /usr/local, though this is just a waste of time because you will almost certainly have to re-install packages, especially if they add files to the /etc directory.

I just copy all the packages that I make to a directory ~/otherpkg on my home partition and after I have a new install working I just do samac

When I ran winecfg, I was asked if I wanted to install Gecko - I selected yes.

I think another method is to download the winetricks script (it's on the third party list on the wine homepage), then do a "chmod +x winetricks", then just "./winetricks gecko".

As for the md5sum in the "wine.info" file, I've never bothered changing that.

My steps normally are;
1) Download the slackbuild file.

wget http://slackbuilds.org/slackbuilds/1...em/wine.tar.gz

2) Extract

tar zxvf wine.tar.gz

3) Change directory in to the folder that was just created ("cd wine" or whatever).

cd wine

4) Obtain the source code (Source code URL normally on the slackbuild page)

wget http://ibiblio.org/pub/linux/system/...1.1.37.tar.bz2

5) Edit the slackbuild executable file if needed. ("wine.SlackBuild" in this case)

pico -w wine.SlackBuild

(Or your favorite text editor.) Here I would edit the line from;
VERSION=1.1.24
to
VERSION=1.1.37
(and save/exit the editor)
6) Launch the script...

./wine.SlackBuild

.. go get some tea, browse the web, wait, etc.

The package will be in /tmp/ (normally with SBo in the filename)... I move this to a custom folder, and install it.

Duly noted and I concur where system files are involved.
This sounds like a well-organized way to do an upgrade.
And those packages that you have made are made using SlackBuild
as in the wine.SlackBuild file that we have been discussing?
thanks again
tim