Hi folks,
I've installed Wine RPM from RH 8.0. _*Very*_ impressed with the goal, and the progress so far! (Red Hat seem only to offer an RPM of the 20020605 version, so I am hoping they'll release a newer one soon.)
In trying to get applications working, I have a small number of tips, workarounds, queries about peculiar Wine behaviour, and so forth.
I can't find anything relevant in the Codeweavers 'zilla database, but I'm not sure I've been very successful at asking the right questions anyway ;)
Is this a reasonable place to present my findings and/or ask if others have encountered similar issues? The issues are application-related, but they often seem to be related to Wine configuration and/or anomalies (?bugs) so that's why I tried this mailing list first. (I can't get to a news feed at the moment.)
I've installed Wine RPM from RH 8.0. _*Very*_ impressed with the goal, and the progress so far! (Red Hat seem only to offer an RPM of the 20020605 version, so I am hoping they'll release a newer one soon.)
Hi, that version is over half a year old. Compiling from source is a bit harder than using RPMs, but not much. If you can keep up with CVS then upgrading is pretty easy as well.
Is this a reasonable place to present my findings and/or ask if others have encountered similar issues? The issues are application-related, but they often seem to be related to Wine configuration and/or anomalies (?bugs) so that's why I tried this mailing list first. (I can't get to a news feed at the moment.)
For app specific stuff, the appdb.winehq.com is probably a good place. Given how old the copy you're using is however, I'd recommend you upgrade. You may find your tips are obsolete :)
On Wed, 2003-03-12 at 17:28, Mike Hearn wrote:
Hi, that version is over half a year old. Compiling from source is a bit harder than using RPMs, but not much. If you can keep up with CVS then upgrading is pretty easy as well.
Yes, I was wondering about this. RH are often quite good at new releases, but perhaps only for security issues or bugs they consider more serious in non-development systems and hence they've not even tried to deliver a newer RPM for Wine. Oh well, I might have to try biting the bullet. Very badly pressed for time at present though :(
For app specific stuff, the appdb.winehq.com is probably a good place.
Sure, I'll use that - I'd poked around already, but wasn't sure if it wanted lots of my comments adding - plus, some of my queries are for several app's as they relate to shared components.
btw, I have noticed that my ~/.wine/config gets rewritten sometimes, losing my PATH setting. Am I mad, or is this something you know to be intentional (without effort or research).
You may find your tips are obsolete :)
:)
James a écrit:
On Wed, 2003-03-12 at 17:28, Mike Hearn wrote:
Hi, that version is over half a year old. Compiling from source is a bit harder than using RPMs, but not much. If you can keep up with CVS then upgrading is pretty easy as well.
Yes, I was wondering about this. RH are often quite good at new releases, but perhaps only for security issues or bugs they consider more serious in non-development systems and hence they've not even tried to deliver a newer RPM for Wine. Oh well, I might have to try biting the bullet. Very badly pressed for time at present though :(
Wine has not been updated for the latest beta (Phoebe), and it's not in Rawhide anymore. I think it has to do with a change to glibc-2.3 and a patch to the kernel (that same issue was discussed here, and affects Debian unstable or testing I think).
Or (shamelessly plugging myself), you can install the RPMs I maintain for RH8.0 at http://www.mecano.gme.usherb.ca/~vberon/wine/. They're based on RedHat latest (20020605), so the upgrade should go pretty smoothly.
Vincent
On Wed, 2003-03-12 at 18:26, Vincent Béron wrote:
Wine has not been updated for the latest beta (Phoebe), and it's not in Rawhide anymore. I think it has to do with a change to glibc-2.3 and a patch to the kernel
Ah, sounds tricky.. I hope RH aren't dropping it completely, yike..
Or (shamelessly plugging myself), you can install the RPMs I maintain for RH8.0 at http://www.mecano.gme.usherb.ca/~vberon/wine/.
Oh, maintaining RPM's for those of us too timid to try building seems reason enough to be allowed to plug yourself! Thanks for details, I'll take a look. Maybe Red Hat could pay you for your services?
On Wed, 2003-03-12 at 18:33, James wrote:
On Wed, 2003-03-12 at 18:26, Vincent Béron wrote:
Wine has not been updated for the latest beta (Phoebe), and it's not in Rawhide anymore. I think it has to do with a change to glibc-2.3 and a patch to the kernel
Ah, sounds tricky.. I hope RH aren't dropping it completely, yike..
I seem to recall in the Phoebe release notes it was dropped yes, the reason given was "resource constraints". I can't really say I blame them, Wine moves so fast that a 6 month old RPM isn't really very useful for bug reports etc, and compiling from the source is a basic Linux skill at the moment anyway. Sucks, but there we go, they only have so much space.
James wrote:
On Wed, 2003-03-12 at 17:28, Mike Hearn wrote:
Hi, that version is over half a year old. Compiling from source is a bit harder than using RPMs, but not much. If you can keep up with CVS then upgrading is pretty easy as well.
Yes, I was wondering about this. RH are often quite good at new releases, but perhaps only for security issues or bugs they consider more serious in non-development systems and hence they've not even tried to deliver a newer RPM for Wine. Oh well, I might have to try biting the bullet. Very badly pressed for time at present though :(
Since I recently provided instructions elsewhere, here is a copy. I would ignore the tarball method mentioned in the wine documentation; I consider it more trouble than it is worth. This takes only a few minutes, other than the time spent waiting for the Wine compile to complete.
First uninstall the Wine that you have (you can always reinstall it later if desired). Then..
Create the file ~/.cvspass and put in the line: :pserver:cvs@cvs.winehq.com:/home/wine Ah<Z
Create the file ~/.cvsrc and put in: cvs -z 3 update -PAd diff -u
Type "cvs checkout wine", and in a few minutes (assuming a reasonable internet connection) you should have a complete Wine tree. CD into it and type "./tools/wineinstall", or do it manually: ./configure make depend make make install (as root)
And you should then be ready to go. That really should be all there is to it. Then in the future to update, you just CD into the wine directory and type "cvs update", and then redo the last four steps above.
On Wed, 2003-03-12 at 18:28, Duane Clark wrote:
Since I recently provided instructions elsewhere, here is a copy. I would ignore the tarball method mentioned in the wine documentation; I consider it more trouble than it is worth. This takes only a few minutes, other than the time spent waiting for the Wine compile to complete.
Great, thanks for the copy of details. I'll file them away for when I get a moment. It's a little while since I last tried building anything manually, and had compatibility issues back then, so I avoid it when I can, plus I noticed some stuff in the knowledgebase about this so felt i should approach with caution!
James wrote:
Great, thanks for the copy of details. I'll file them away for when I get a moment. It's a little while since I last tried building anything manually, and had compatibility issues back then, so I avoid it when I can, plus I noticed some stuff in the knowledgebase about this so felt i should approach with caution!
Ah yes, you are running RH8. I do seem to recall some mention of problems there.
-
Duane Clark -
James -
Mike Hearn -
Mike Hearn -
Vincent Béron