Forums » Linux
You're never going to believe this.
I just updated the updater. To use gtk 2.0 instead of gtk 1.2.
One of the upshots of this is that I linked against a version glibc from this millennium. So the extreme measures I took to ensure binary compatiblity are no longer in effect for the updater. I doubt anyone will have a problem, but if the updater no longer runs after the update tonight, please let me know. Do an ldd ~/.vendetta/update.rlb if you have problems getting it to run and post the result here.
So far this works for me on two different gentoo boxes and my ubuntu box.
As a workaround, if the new updater won't launch, you can rm ~/.vendetta/update.rlb and run the original 'vendetta' binary (the one that you installed with the installer shell script, not ~/.vendetta/vendetta) with the -phase2 option to skip updating the updater.
One of the upshots of this is that I linked against a version glibc from this millennium. So the extreme measures I took to ensure binary compatiblity are no longer in effect for the updater. I doubt anyone will have a problem, but if the updater no longer runs after the update tonight, please let me know. Do an ldd ~/.vendetta/update.rlb if you have problems getting it to run and post the result here.
So far this works for me on two different gentoo boxes and my ubuntu box.
As a workaround, if the new updater won't launch, you can rm ~/.vendetta/update.rlb and run the original 'vendetta' binary (the one that you installed with the installer shell script, not ~/.vendetta/vendetta) with the -phase2 option to skip updating the updater.
Tiny issue.
When the (nice) new updater updates the main executable, it clears the execution bit.
"chmod +x ~/.vendetta/vendetta" is the workaround, but maybe you can automate that.
When the (nice) new updater updates the main executable, it clears the execution bit.
"chmod +x ~/.vendetta/vendetta" is the workaround, but maybe you can automate that.
BOO! now xmms will feel lonely!
Seems to work on slackware too, they use a slightly older glibc.
scrolling fixed!
Does it still corrupt the game files when it runs out of disk space?
EDIT: I don't haver any executability problems
Seems to work on slackware too, they use a slightly older glibc.
scrolling fixed!
Does it still corrupt the game files when it runs out of disk space?
EDIT: I don't haver any executability problems
Very, very, very nice..
It works quite well on AMD64 on Gentoo.
Thanks
It works quite well on AMD64 on Gentoo.
Thanks
Syylk: When you click 'Play Vendetta', it sets the execution bits. Same behavior as the old updater.
mr_spuck: Yes, it still does... There isn't a portable way of getting free disk space, and I was too tired to figure it out last night.
mr_spuck: Yes, it still does... There isn't a portable way of getting free disk space, and I was too tired to figure it out last night.
My bad.
I never use the updater to start the game, but just to... err... update the files. :)
I have this nasty habit of wrapping everything in launching scripts from my ~/bin dir. In case of vendetta, to disable the caps lock key, and reenable it when I quit the game.
I never use the updater to start the game, but just to... err... update the files. :)
I have this nasty habit of wrapping everything in launching scripts from my ~/bin dir. In case of vendetta, to disable the caps lock key, and reenable it when I quit the game.
COOL!
Now all I need to do is get back to college so I can turn on my Linux box and test it. This is 64-bit-clean, right?
Now all I need to do is get back to college so I can turn on my Linux box and test it. This is 64-bit-clean, right?
I am releasing a 1.7.14.2 with a version of the updater that doesn't directly link against pango (it's not like our code is using it... if gtk has it linked in, it will use it).
WE WANT LEEBS: just rm ~/.vendetta/update.rlb and run the launcher (usually ~/bin/vendetta). That will download the corrected updater without running the broken one.
WE WANT LEEBS: just rm ~/.vendetta/update.rlb and run the launcher (usually ~/bin/vendetta). That will download the corrected updater without running the broken one.
Hello!
Could You also upgrade client in Download sections so packages in distributions could remove gtk-1* dependency?
On other hand information on Download section is also inaccurate as client does not have size of approximate size of 110MB. I would be very grateful for these updates.
I will pass info to Gentoo bugzilla about this change.
Could You also upgrade client in Download sections so packages in distributions could remove gtk-1* dependency?
On other hand information on Download section is also inaccurate as client does not have size of approximate size of 110MB. I would be very grateful for these updates.
I will pass info to Gentoo bugzilla about this change.
We are working on that right now, moloh.
Thanks.
With my font settings the default size of the window is not wide enough to fit one line of text as it is formatted in the changelog, causing the last word of text to flow over to next line, and then the line break going to next line again, which makes me end up with many lines in the changelog, and half of them only having one word. Could you make the window somewhat wider please?
Otherwise working fine here, Slackware 11.0 x86. Job well done.
Otherwise working fine here, Slackware 11.0 x86. Job well done.
Working on gentoo ~amd64 for me with the 64-bit client.
Also, I love the progressbar for "Verifying files". On the other updaters, it just says "verifying files" with no estimate, and sometimes it takes a minute or two. But we get a progressbar! woot!
Also, I love the progressbar for "Verifying files". On the other updaters, it just says "verifying files" with no estimate, and sometimes it takes a minute or two. But we get a progressbar! woot!
Erm, that's what I just said.
Works nicely here too, Gentoo ~x86 + cvs
rogue: yeah, I just added that since the "verifying files" hangup was annoying. The other updaters just need to be recompiled and released to get that feature too.
Antz: You can resize your window, since you resized your font. :)
I'm not sure what the best way to handle that situation is.. I could try to get the font metrics and make it 60 ems wide or something (I wrap the changelog to 60 characters). But the window will be open already at that point.
Antz: You can resize your window, since you resized your font. :)
I'm not sure what the best way to handle that situation is.. I could try to get the font metrics and make it 60 ems wide or something (I wrap the changelog to 60 characters). But the window will be open already at that point.
Cool. Works now. Thanks a1k0n
Ah, never mind, it is not important and not worth the time if it will need thinking, put it at the bottom of the todo for the next installer iteration. Resizing it is not (much of) a hassle for me.