[Warzone-dev] Fixing 'make dist'

2009-03-15 Thread Per Inge Mathisen
When changing and removing files, will you please check that you do not break 'make dist'? All you (usually) need to do is to list the correct headers in noinst_HEADERS in Makefile.am However, right now the mods are giving me problems. The issue I get is: make[4]: *** No rule to make target `aiv

Re: [Warzone-dev] 2.2 alpha/beta changes

2009-03-15 Thread Elio Gubser
Am Sonntag, den 15.03.2009, 13:15 -0400 schrieb bugs buggy: > Was wondering what port should we change 2.2 to use? > 2.0.x was using: (do we still have a 2.0 lobby server?) > gameserver_port: > masterserver_port: 9998 > 2.1 is using: > gameserver_port: > masterserver_port: 9997 > Then a

Re: [Warzone-dev] 2.2 alpha/beta changes

2009-03-15 Thread Per Inge Mathisen
On Sun, Mar 15, 2009 at 6:15 PM, bugs buggy wrote: > Then there is port 2100 :) Too good to pass over. IMHO. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev

Re: [Warzone-dev] 2.2 alpha/beta changes

2009-03-15 Thread Dennis Schridde
Am Sonntag, 15. März 2009 18:15:32 schrieb bugs buggy: > Was wondering what port should we change 2.2 to use? > 2.0.x was using: (do we still have a 2.0 lobby server?) > gameserver_port: > masterserver_port: 9998 > 2.1 is using: > gameserver_port: > masterserver_port: 9997 > > Do we swit

Re: [Warzone-dev] 2.2 alpha/beta changes

2009-03-15 Thread Zarel
2009/3/15 bugs buggy : > Was wondering what port should we change 2.2 to use? > 2.0.x was using:  (do we still have a 2.0 lobby server?) > gameserver_port: > masterserver_port: 9998 > 2.1 is using: > gameserver_port: > masterserver_port: 9997 > > Do we switch to 1 for 2.2 & trunk?  (N

Re: [Warzone-dev] 2.2 alpha/beta changes

2009-03-15 Thread Kreuvf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 bugs buggy wrote: > Do we switch to 1 for 2.2 & trunk? (Note, this will be the last > switch, since we will have version checking code in the codebase) > 9996 is used by a trojan (W32.Sasser.Worm), so I doubt we want to use > that port-- I know a

[Warzone-dev] 2.2 alpha/beta changes

2009-03-15 Thread bugs buggy
Was wondering what port should we change 2.2 to use? 2.0.x was using: (do we still have a 2.0 lobby server?) gameserver_port: masterserver_port: 9998 2.1 is using: gameserver_port: masterserver_port: 9997 Do we switch to 1 for 2.2 & trunk? (Note, this will be the last switch, since

Re: [Warzone-dev] Release 2.2 (with port change) or go with 2.1.3 + port change or ?

2009-03-15 Thread Freddie Witherden
Hi, On Sun, 2009-03-15 at 09:02 +0100, Kreuvf wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Freddie Witherden wrote: > > I'd rather just use the SVN revision of the game. It is simpler. > What do you do when switching to another VCS? That value must be > VCS-independent. And if I u

Re: [Warzone-dev] Release 2.2 (with port change) or go with 2.1.3 + port change or ?

2009-03-15 Thread Kreuvf
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Freddie Witherden wrote: > I'd rather just use the SVN revision of the game. It is simpler. What do you do when switching to another VCS? That value must be VCS-independent. And if I understand the git docs correctly (haven't really read much of it :X)