Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Right now, I have wine 0.9.42 installed and it works great with the programs that I have installed.
The thing is, I need to update it but I need to keep the older wine around and able to run for at lest two particular programs (the art programs called, openCanvas 1.1, and ArtRage 1 and 2.)
In the past, I have tried to have 2 versions of wine (0.9.12 and 0.9.42) and I tried following the instructions given me in wine's forums on google groups: I had compiled it to install into its own folder, I had exported the library paths, I had even made a specific .wine042 folder for it to use when I needed to run winecfg to configure that particular version. But no matter what I did, both versions wanted to take over/use the the same .wine folder.
I've also read that you can run wine without having installed it? Really? How is that done? How would you install a program into that wine when it has not been installed so as to test it out? It would be great if I could do that to test if it is compatible with the programs I want to run.
Last edited by gymnart; 03-05-2010 at 12:23 PM.
I've never tried running two different versions at once, so there are no details here, but as I understand it, the secret is to first launch separate wineservers, each configured with it's own wineprefix. Then you direct each program you launch to connect to the appropriate wineserver. It all comes down to the commands you use to launch everything with.
So, if I understand it, I can install a new wine in it's own folder (for 1.1.36) (./configure --prefix=/home/<username>/Wine1.1.36), then do I: make depend; make; make install or should I leave out the "make depend"?
Then I should use the WINEPREFIX command to install the desired program as you said, right? If I wanted to run winecfg for the newer version, would I have to use the WINEPREFIX command too?
You can install wine wherever you want as long as it doesn't overwrite the other wine, and you know which one is which.
wine defaults to 'WINEPREFIX=~/.wine' but if you want a different one so that there isn't a conflict you have to run it as I mentioned above. You can have one wine use the default and the other use another.
I'm still wondering if make depend is needed. I didn't use it last time I installed it so could not using it cause problems?
Regarding the .wine file for the newer WINE, could it be in the /home/<username>/Wine1.1.36 folder and have the same name or should it be named something else? Will it insist on being in /home/<username>?
Now, has wine's dependences changed a lot since 0.9.42, as in requiring much newer versions? I'm running an older SuSE kernel so I can't get the newest dependencies even if I wanted to.
This will install wine in your home folder, is this what you want ? You will have to run wine from here because unless you add it to the $PATH it will not be seen. The executable would probably be at /home/<username>/Wine1.1.36/bin/wine so you would need to run that every time.
Thanks for clearing that up, that's what I needed.
I'm not quite sure about your statements,
"If you added wine to your PATH, then you'd just use wine instead of the whole path."
"unless you add it to the $PATH it will not be seen."
I thought I had put wine in my PATH for executing the program. Is $PATH where the system wants to look for it?
Does that mean I would have to export library paths each time I wanted to run the new wine or something? That's where I got totally confused the first time I had tried this (and thus failed in my attempt back in about 2007).
It is set automatically by some script somewhere during startup. If wine is not located in one of these directories, you'll have to specify the full path. But, remember that if you run two versions of wine, you can't have both versions called 'wine' in your PATH, so I would first try running it with the full path to be safe.
Running it with the full path seems easier anyway. I kinda thought that you couldn't have 2 different wines in your path.
I am going to try this when I get more time (gotta get the kid from school early today and tomorrow and then referee him and his sister [from fighting] during the weekend.)
If there's problems, I'll be sure to post here again, and if I'm successful, I'll let ya know that too.