The text saying "you need to have a valid steam account" after emerging halflife-steam is wrong. Valve has removed the need for it. There is also no rc-script for the game server. I've created one at http://gentoo-wiki.com/HOWTO_Halflife_Dedicated_Server_%28CounterStrike%29 which can be used. Reproducible: Always Steps to Reproduce: 1. #emerge halflife-steam 2. try to start it :)
Created attachment 72920 [details] halflife-steam.tar.bz2 it's been a long time since i ran a halflife server ... try this ebuild for me please
There is a typo in your ebuild: The line "-e "s:@GAMES_USER@:${GAMES_DED_USER}:" \" should be "-e "s:@GAMES_USER@:${GAMES_USER_DED}:" \" I think (this is a cosmetical change) nowadays the most used steam gameserver is "Counter-Strike: Source" so we should give a hint how to install it, like: einfo '3. Install the game of your choice:' einfo " steam -command update -game "Counter-Strike Source" -dir ${GAMES_PREFIX_OPT}/halflife"
cstrike is for old 1.6 then ? is 'css' the shortname for counterstrike source ?
No. There is no short name for Counter-Strike Source. You really have to type "Counter-Strike Source" to install the game. And yes, cstrike ist the old one. Here is the output of ./steam -command update -game: Checking bootstrapper version ... Updating Installation ** 'game' options for Source DS Install: "Counter-Strike Source" "dods" "hl2mp" ** 'game' options for HL1 DS Install: "cstrike" "czero" "dmc" "dod" "gearbox" "ricochet" "tfc" "valve" HLDS installation up to date
thanks, added all to cvs, bug me if i screwed it up ;)
Just one question. Why the fsck is this ebuild masked with "-* x86" keywords? It does work of course with amd64, doesn't it? Are there bugs known (Changelog doesn't give any information about bugs etc)? Well, at last there is also a x86_64-optimized binary since 2 weeks, so please fix the keywords, thanx.
Wow... such wonderful rudeness... Did it ever occur to you that it doesn't have any KEYWORDS for amd64 because nobody ever tested it on the platform and we aren't going to support something that is untested? Anyway, this bug has *nothing* to do with amd64 KEYWORDS, so feel free to file a new bug if you think they should be added.
