Fwd: [cod] COD5-Plus Centos 5.2 wine/cod installer final

[dnk]

Hey guys, I am starting work on the updated version which will not  
have to compile wine, but I am wondering if you guys feel there is a  
need to maintain the compile option. My first thought is "no" as if  
and when the bins come out, I will likely just update the script to  
just perform a COD5 server linux bin installer - which in turn would  
then likely be able to support pretty much any linux version. Although  
after this one, i am playing with the thought of porting the script to  
include debian support. But that possibly may not happen until early  
January. Might squeeze it in if i can though.

Just curious before i start writing.

d



Begin forwarded message:
>
>
>> From: Dnk <d.k.emaillists at gmail.com>
>> Date: December 13, 2008 8:41:16 AM PST (CA)
>> To: "cod at icculus.org" <cod at icculus.org>
>> Subject: Re: [cod] COD5-Plus Centos 5.2 wine/cod installer final
>>
>> I am not too familiar with debian at all, but I imagine it would  
>> not be hard to do. It would mostly be a matter of finding out what  
>> the packages are named in debian, and replacing the CentOS related  
>> install commands with debian specific ones.
>>
>> Now to do that, I have a few quick questions regarding debian.
>>
>> 1) installer for debian itself, or ubuntu?
>>
>> 2) which version? I would prefer to use the latest and move  
>> forward, but I am not familiar with the debians to know which one  
>> most people would be using. I don't want to end up maintaining a  
>> boat load of versions of this script. But don't mind have a target  
>> version for CentOS, and one for a debian style system.
>>
>> 3) would you be looking for the script to compile wine as well, or  
>> just install from a repository (if available)? Thus making it more  
>> of just a setup script for cod5 itself?
>>
>>
>> 4) and on the above note (3), one I have the rpms available under  
>> CentOS for wine, is there any value in keeping the option to  
>> compile wine, or should I just drop it and go rpm only, thus making  
>> the script more of a cod only installer?
>>
>>
>>
>> Also moving forward, if and when certain *ahem* "files" (bins)  
>> become available, I will be modifying the script to just automate  
>> an install of that. And with those, I am sure I will be able to  
>> write it to work on almost any Linux system as it would probably  
>> become more cod specific.
>>
>> Is there even value in that for the community?
>>
>> Dnk
>>
>> Sent from my iPhone
>>
>> On 13-Dec-08, at 1:12 AM, "Smearlap" <smearlap at fresh-gaming.de>  
>> wrote:
>>
>>> Could you also modify the script to make it work under Debian?
>>>
>>> ----- Original Message ----- From: "dnk" <d.k.emaillists at gmail.com>
>>> To: <cod at icculus.org>
>>> Sent: Saturday, December 13, 2008 7:51 AM
>>> Subject: [cod] COD5-Plus Centos 5.2 wine/cod installer final
>>>
>>>
>>>> This document walks you through the install process to get COD5  
>>>> (World
>>>> at War) server running under wine on CentOS5.2 With no "X"
>>>> Environment. Included is a custom bash shellscript installer to do
>>>> most of the dirty work at the terminal. It will fetch the required
>>>> files (including COD5 Server files, Wine, etc), compile wine  
>>>> (without
>>>> x support), and configure a server.cfg and startServer.sh script.  
>>>> Upon
>>>> discussion on the CentOS mailing list, Dag Wieers (one of the
>>>> packagers involved with the CentOS project and major contributor to
>>>> RPMforge) will be rolling up a nice wine 1.1.10 RPM (needed for  
>>>> COD5
>>>> to work under wine)! So once that is available after testing, the
>>>> install script will give you the option to either still compile  
>>>> wine,
>>>> or use the RPM (MUCH faster, and less dev tools to install).  
>>>> Providing
>>>> there are no show stopping issues with the RPM.
>>>>
>>>> Mirror away!
>>>>
>>>>
>>>> Dustin
>>>>
>>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>>
>>>> ---
>>>> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
>>>> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi? 
>>>> 38
>>>
>>>
>>> ---
>>> To unsubscribe, send a blank email to cod-unsubscribe at icculus.org
>>> Mailing list archives: http://icculus.org/cgi-bin/ezmlm/ezmlm-cgi?38
>>>
>>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20081215/23139bca/attachment.htm>