irclog2html for #bzflag on 20030912

`00:02.47`	`*** join/#bzflag Spiff (Spiff@12-222-147-141.client.insightBB.com)`
`00:03.05`	`Spiff`	`:-)`
`00:27.47`	`Legolas`	`hey spiff`
`00:36.04`	`Legolas`	`bye bye`
`00:36.59`	`CIA`	`03brlcad * 12bzflag/src/bzfs (bzfs.cxx): only need to get the arbiter once per external scope -- make it static`
`00:37.41`	`*** join/#bzflag bryjen (bryjen@ky-owensboro1a-242.owboky.adelphia.net)`
`00:54.22`	`CIA`	`03brlcad * 12bzflag/src/common (VotingBooth.cxx): er, increment index _AFTER_ recording the vote`
`00:59.04`	`learner`	`hehe, cool -- bug fixed`
`01:12.30`	`*** join/#bzflag bryjen (bryjen@ky-owensboro1a-242.owboky.adelphia.net)`
`01:44.14`	`*** join/#bzflag Justin_ (~justin@H251-225.FREEDOM.resnet.albany.edu)`
`02:27.56`	`*** join/#bzflag KR (~k@cae168-234-054.sc.rr.com)`
`02:28.03`	`KR`	`hi all`
`02:28.42`	`learner`	`howdy, how goes it?`
`02:28.48`	`bzgirl`	`hi kr`
`02:28.49`	`KR`	`perty good`
`02:28.54`	`KR`	`hi fizz`
`02:29.05`	`bzgirl`	`:)`
`02:29.18`	`learner`	`it was another good boating day on this coast..`
`02:29.18`	`KR`	`attempting to get my printer working from this laptop - Rute time! ;)`
`02:29.31`	`KR`	`u on the left coast or east?`
`02:29.31`	`Justin_`	`my bzflag broke in 2.6 :( sound doesn't play anymore`
`02:29.41`	`learner`	`east -- ways north from you`
`02:29.55`	`KR`	`new england?`
`02:30.00`	`learner`	`md`
`02:30.09`	`KR`	`2.6 what?`
`02:30.10`	`bzgirl`	`Justin_: 2..6?`
`02:30.16`	`KR`	`nah u are right by chiko`
`02:30.23`	`KR`	`"n":)`
`02:30.26`	`Justin_`	`2.6.0-test5`
`02:30.36`	`learner`	`lol -- works with or without the "n" :)`
`02:30.44`	`KR`	`lol`
`02:30.47`	`Justin_`	`haven't tried 2.5.x or 2.6.x in a looong time, so I wonder what did it`
`02:31.05`	`Justin_`	`strange because sound works in everything else but bzflag`
`02:31.13`	`KR`	`Justin - what 2.6 - a lin distro?`
`02:31.26`	`Justin_`	`uh no. the kernel`
`02:31.31`	`KR`	`ahh - doh`
`02:31.34`	`KR`	`:)`
`02:31.41`	`bzgirl`	`so after new kernel no sound in bz?`
`02:31.51`	`Justin_`	`yeah`
`02:32.05`	`bzgirl`	`do you have sound in other games? tuxracer?`
`02:32.17`	`KR`	`xmms?`
`02:32.20`	`Justin_`	`yeah, everything else is normal`
`02:32.34`	`bzgirl`	`what version of bzflag?`
`02:32.53`	`Justin_`	`BZFlag client, version 1.7g2`
`02:33.23`	`KR`	`I had a weird bug in some dist, sound would only work in bzflag after I had fired up and shutdown xmms prior to bzflag - maybe some arts thing`
`02:33.44`	`Justin_`	`not using arts, and I have an audigy so it doesn't matter`
`02:34.03`	`KR`	`nokies`
`02:34.11`	`KR`	`gee - n n n`
`02:34.25`	`KR`	`sry, just got done bz'ing :)`
`02:34.29`	`bzgirl`	`well you really should be running xmms whenever you play, as the built in bzmp3 player is not yet coded :)`
`02:34.38`	`KR`	`:)`
`02:35.18`	`*** join/#bzflag Noodleman (cyber@webirc.caffeine-powered.com)`
`02:35.19`	`KR`	`don't you use /playmp3 in bzflag?`
`02:35.24`	`KR`	`:)`
`02:35.34`	`learner`	`doesn't patlabor owe you that bzg, or was it cappy? :)`
`02:36.13`	`bzgirl`	`no, patlabor221 owes me a server that streams mp3s to the clients, hes working on it :)`
`02:36.45`	`KR`	`just googled bzg blog...`
`02:36.46`	`bzgirl`	`Justin_: what distro? and did you compile bz or install a package of some sort?`
`02:36.52`	`KR`	`guess what came up first? :)`
`02:37.25`	`bzgirl`	`stupid google :)`
`02:37.44`	`Justin_`	`bzgirl: debian unstable`
`02:37.45`	`learner`	`you're kidding :)`
`02:37.51`	`learner`	`~google bzg blog`
`02:37.55`	`Justin_`	`i haven't tried booting the old kernel again, pretty sure it would still work`
`02:38.01`	`Justin_`	`even removed ~/.bzflag`
`02:38.27`	`*** join/#bzflag Noodleman (~tuckerm@procyon.noodleroni.com)`
`02:38.43`	`patlabor221`	`and I am too`
`02:38.47`	`bzgirl`	`Justin_: have you tried building it from source?`
`02:38.53`	`Justin_`	`nope`
`02:38.53`	`patlabor221`	`I just never said what game.`
`02:38.58`	`Justin_`	`don't see how it would matter :)`
`02:39.02`	`learner`	`careful noodle -- he kicks better`
`02:39.11`	`Noodleman`	`learner: hehe`
`02:39.17`	`bzgirl`	`Justin_: no, but its fun`
`02:39.24`	`Justin_`	`:)`
`02:39.45`	`Noodleman`	`the access point i'm on right now is _laggy_`
`02:43.34`	`bzgirl`	`Justin_: try bzflag -echo to see for any errors?`
`02:45.29`	`bzgirl`	`does the bz client have super verbosity like the server's -d -d -d?`
`02:47.06`	`Noodleman`	`l8r`
`02:48.17`	`KR`	`c ya noodle`
`02:48.21`	`bryjen`	`doesn't 2.6 use ALSA instead of OSS?`
`02:48.30`	`KR`	`bzg - jammin some vacuum music..`
`02:48.34`	`KR`	`;)`
`02:49.09`	`KR`	`no pigtails, tho`
`02:50.09`	`bzgirl`	`heh`
`02:51.02`	`learner`	`there's no -d equiv in the client`
`02:52.05`	`learner`	`there is a mute option, though. Justin_ what does the volume setting on the menu say?`
`02:57.35`	`*** part/#bzflag bzgirl (~orchid@toronto-hs-64-26-176-100.s-ip.magma.ca)`
`03:01.50`	`Justin_`	`learner: 10`
`03:02.05`	`learner`	`actually, it's 11 here ;)`
`03:02.29`	`learner`	`hrm`
`03:03.11`	`Justin_`	`maybe my install got screwed...`
`03:03.31`	`learner`	`simple enough to try, but I doubt it`
`03:03.41`	`Justin_`	`well i was hacing 3d problems`
`03:03.51`	`Justin_`	`and i was usig bzflag to test:)`
`03:04.17`	`Justin_`	`yeah, didnt help`
`03:04.59`	`CIA`	`03brlcad * 12bzflag/src/bzfs (2 files): added the ability to keep track of who is allowed to vote`
`03:05.07`	`Justin_`	`heh, i just had my friend install it and he has the same config mostly`
`03:05.26`	`Justin_`	`and his sound doesn't work either`
`03:05.41`	`learner`	`so you both did something wrong :)`
`03:06.13`	`Justin_`	`i don't think so ;)`
`03:06.21`	`Justin_`	`lemme try the oss driver instead`
`03:06.26`	`bryjen`	`is linux 2.6 using ALSA for sound instead of OSS ?`
`03:06.28`	`learner`	`j/k, I'm not sure -- that bit of code isn't my area`
`03:06.40`	`bryjen`	`bzflag uses OSS`
`03:07.19`	`Justin_`	`well I was using alsa in 2.4 too`
`03:07.21`	`*** join/#bzflag TyroneFHornigh (~JBDiGriz@p26.n-sfpop02.stsn.com)`
`03:08.03`	`bryjen`	`hmm ALSA has OSS compatiblity modules, are they loaded now?`
`03:08.17`	`bryjen`	`or maybe they're not as compatible in 2.6`
`03:08.38`	`learner`	`I've heard other reports of alsa not working quite right -- if you can get oss to work, try it instead`
`03:09.23`	`Justin_`	`yeah, it works with oss, not with alsa`
`03:09.26`	`Justin_`	`strange`
`03:09.30`	`Justin_`	`wonder what changed`
`03:10.36`	`KR`	`trouble brewing : http://www.wunderground.com/tropical/tracking/at200313_sat.html`
`03:10.52`	`KR`	`Hurricane Isabel`
`03:11.08`	`KR`	`you on the coast up there learn? :0`
`03:11.11`	`bryjen`	`i'd bet its something in the oss compat stuff of ALSA`
`03:11.24`	`learner`	`see, kr.. should went today or yesterday..`
`03:11.32`	`*** join/#bzflag GrizzlyAdams (~JBDiGriz@p26.n-sfpop02.stsn.com)`
`03:12.28`	`Justin_`	`http://linux.derkeiler.com/Mailing-Lists/Kernel/2003-08/2726.html`
`03:12.30`	`Justin_`	`interseting`
`03:12.32`	`learner`	`I'm real close to the chesapeake -- a mile or two, but not to the coast`
`03:12.39`	`KR`	`goin saturday ;)`
`03:13.26`	`KR`	`the discussion has gone from "Portions of the East Coast may be affected" to "we are sure which portions of the East Coast will be affected"`
`03:13.39`	`KR`	`^aren't sure which`
`03:13.58`	`learner`	`Justin_: lol, i've never thought of bzflag as a kernel sound debug tool :)`
`03:14.10`	`KR`	`:)`
`03:14.34`	`bryjen`	`wow. when pat shuts down, he _shuts_ _down_`
`03:14.49`	`learner`	`damn his peer`
`03:15.33`	`bryjen`	`don't close them sockets, just kill -9 *`
`03:17.54`	`learner`	`I have no patience for shutdown procedures -- if it's not mine I just power cycle the sucker (_especially_ if it's windows)`
`03:20.28`	`learner`	`eep.. I killed CIA`
`03:20.46`	`learner`	`get back here scanline!`
`03:22.32`	`bryjen`	`knocking the legs out from under an already wobbly system. there's a recipe for disaster.`
`03:24.50`	`learner`	`what's the difference between Locked and ReadOnly in the BZDB StateDatabase?`
`03:25.05`	`learner`	`is locked no access?`
`03:25.25`	`bryjen`	`if you're gonna be that way about it, you need to strap one of these to the side of the machine and wire the power cord thru it:`
`03:25.28`	`bryjen`	`http://www.science-city.com/knifeswitch.html`
`03:26.02`	`*** join/#bzflag patlabor221 (~jeffm@adsl-64-172-197-72.dsl.lsan03.pacbell.net)`
`03:26.03`	`*** mode/#bzflag [+o patlabor221] by ChanServ`
`03:26.11`	`learner`	`hehe`
`03:32.30`	`purple_cow`	`yay`
`03:32.36`	`*** join/#bzflag CIA (CIA@cia.utility.freenode)`
`03:32.47`	`purple_cow`	`irc from a Z C700`
`03:33.09`	`patlabor221`	`wireless?`
`03:33.15`	`purple_cow`	`yup`
`03:33.19`	`patlabor221`	`keen`
`03:33.23`	`patlabor221`	`hard to use?`
`03:33.29`	`purple_cow`	`happens to be scanline's`
`03:33.44`	`patlabor221`	`you could "apropriate" it`
`03:33.52`	`purple_cow`	`heh`
`03:38.31`	`*** join/#bzflag Bagheera (~Bagheera@pool-162-84-20-103.sal.east.verizon.net)`
`03:39.11`	`CIA`	`03brlcad * 12bzflag/src/bzfs (bzfs.cxx): do not let cmdSet (/set) try to set variables that are not ReadWrite; output an message if not writeable`
`03:39.12`	`CIA`	`03brlcad * 12bzflag/src/bzfs (bzfs.cxx): instead of interactively updating a player count, tell the arbiter who is allowed to vote when the poll is created; auto vote for the poller; disallow poll creation when it will ultimately fail due to not enough players`
`03:39.12`	`CIA`	`03brlcad * 12bzflag/src/bzfs (bzfs.cxx): make the voting arbiter read-only to prevent /set poll 12345678 nasty :)`
`03:39.25`	`Bagheera`	`good night all`
`03:39.31`	`learner`	`howdy bags`
`03:39.37`	`learner`	`g'night bags :)`
`03:42.16`	`learner`	`Well, well.. ladies and everyone else, I do believe poll voting now has all of the features that I had planned to get in prior to our 1.9 release!`
`03:42.33`	`learner`	`it might even work ;)`
`03:42.48`	`purple_cow`	`wheedle`
`03:43.39`	`learner`	`it should now only allow the players that are around upon a poll creation to vote in the poll`
`03:56.52`	`*** join/#bzflag SGIa (~SGI@bgp01138bgs.sothfd01.mi.comcast.net)`
`03:57.09`	`SGI`	`sure Im`
`03:57.13`	`SGI`	`hello`
`03:57.21`	`SGI`	`~seen dtremenak`
`03:57.25`		`dtremenak <~DTRemenak@host-225-121.dialup.innercite.com> was last seen on IRC in channel #bzflag, 4d 4h 27m 18s ago, saying: 'then you could say SW doesn't affect shots, just the guidance system'.`
`04:00.06`	`SGI`	`hello???`
`04:00.12`	`SGI`	`hi SGi how are you`
`04:00.23`	`SGI`	`good thank you for ask me`
`04:00.38`	`*** join/#bzflag TyroneFHornigh (~JBDiGriz@p26.n-sfpop02.stsn.com)`
`04:00.40`	`learner`	`hi sgi`
`04:00.59`	`SGI`	`hi`
`04:01.18`	`SGI`	`sorry im really busy right now Im talking with SGI`
`04:01.29`	`patlabor221`	`so we can see`
`04:01.42`	`patlabor221`	`seems like he's beeing pissy tho`
`04:01.53`	`TyroneFHornigh`	`I thought pat had the issues with voices`
`04:01.59`	`SGI`	`now someone..ill kick me out for my high stupidity`
`04:02.22`	`SGI`	`pissy????`
`04:02.31`	`learner`	`please don't sgi -- you'll probably just end up kicking me again :D`
`04:02.42`	`SGI`	`ehi that it was a mistake`
`04:02.48`	`learner`	`hehe`
`04:02.52`	`purple_cow`	`?win 5`
`04:03.21`	`SGI`	`question`
`04:03.35`	`SGI`	`I want run a random map server`
`04:03.48`	`SGI`	`I have -g and -time`
`04:04.04`	`SGI`	`but I have problem with the world`
`04:04.20`	`SGI`	`its possible to have the maps in one conf file`
`04:04.33`	`patlabor221`	`BZ only reads one map ever`
`04:04.39`	`patlabor221`	`you need a script to change the worlds`
`04:04.42`	`patlabor221`	`or something`
`04:05.20`	`SGI`	`I wrote one it was just a repeated "about 22 times"`
`04:05.33`	`SGI`	`bzfs -g -time 4000 and etc`
`04:05.36`	`patlabor221`	`so have it change the map`
`04:08.06`	`learner`	`sgi: http://brlcad.org/tmp/bzserver2.sh is a simple script that will restart the same server over and over; duplicate the guts of the while loop for each map you want and you should be good to go`
`04:09.12`	`SGI`	`thanks ...Ill kick you out right now`
`04:09.25`	`learner`	`:)`
`04:09.44`	`SGI`	`I wrote one bat file with all maps`
`04:09.55`	`SGI`	`but it was really instable`
`04:09.58`	`patlabor221`	`bat file?`
`04:09.59`	`learner`	`oh, windows?`
`04:10.10`	`SGI`	`yes`
`04:10.20`	`patlabor221`	`then that script will not work`
`04:10.22`	`learner`	`that script won't work with windows, but the idea is similar for a bat file`
`04:10.45`	`patlabor221`	`vba script the shell to launch it :)`
`04:10.46`	`SGI`	`just write a text file -bzfs -g - time -admi etc`
`04:10.52`	`SGI`	`saved a bat`
`04:10.53`	`learner`	`isn't there a bzbb topic that has an example bat file?`
`04:11.00`	`patlabor221`	`then put a difrent map with each one.`
`04:11.31`	`*** join/#bzflag GrizzlyAdams (~JBDiGriz@p26.n-sfpop02.stsn.com)`
`04:13.47`	`KR`	`well, printer probs solved - time for a lttle Ducati fraggin, then bed - g'nite all - and Hello and Bye, SGI :)`
`04:13.58`	`SGI`	`bye good nite`
`04:16.31`	`CIA`	`03brlcad * 12bzflag/src/bzfs (2 files): added introspection into the arbiter to obtain yes/no/abstention counts`
`04:17.50`	`*** join/#bzflag jbdigriz (~JBDiGriz@p26.n-sfpop02.stsn.com)`
`04:20.17`	`JetBlack`	`Ok, I say we blow this thing, everyone get there stuf together....`
`04:21.20`	`TyroneFHornigh`	`If this connection drops again, I'm giving up for the night.`
`04:22.19`	`JetBlack`	`"if that don't prove the powers of kung-fu, nothing will!!"`
`04:22.45`	`JetBlack`	`wtf is stipe?`
`04:23.07`	`Stripe`	`Stripe, Spike, Mohawk, The Brain, ...`
`04:23.17`	`JetBlack`	`?`
`04:23.23`	`JetBlack`	`no, you should be Edward`
`04:26.44`	`aMeatPopsicle`	`no,I'm just rather melencolly`
`04:27.00`	`aMeatPopsicle`	`and it just came to mind.`
`04:27.11`	`aMeatPopsicle`	`"sir, are you classified as human?`
`04:27.47`	`aMeatPopsicle`	`ouch`
`04:27.55`	`aMeatPopsicle`	`autowash!`
`04:28.31`	`EdmundEdmund`	`did cap disappear?`
`04:29.31`	`aMeatPopsicle`	`he cowed`
`04:32.12`	`EdmundEdmund`	`I like the new desk pictures with clickables. ;^)`
`04:32.26`	`aMeatPopsicle`	`I need to finish it`
`04:32.34`	`aMeatPopsicle`	`it takes longer to make them now`
`04:32.56`	`aMeatPopsicle`	`tho tho I did find a way to automate the "bubble" parts`
`04:34.39`	`EdmundEdmund`	`Are we any closer to release, or are we still waiting for a few items.`
`04:35.34`	`aMeatPopsicle`	`well one thing got bumped off the todo list`
`04:35.48`	`EdmundEdmund`	`Was it done or just bumped off`
`04:35.57`	`aMeatPopsicle`	`bumped`
`04:36.04`	`aMeatPopsicle`	`imposible for 1.9`
`04:36.50`	`EdmundEdmund`	`The gameinfo requests are still there, although nobody is working on them`
`04:37.11`	`EdmundEdmund`	`The bzadmin help/man is gone`
`04:37.30`	`aMeatPopsicle`	`it was the "client pick spawn"`
`04:37.45`	`aMeatPopsicle`	`there should be 2 things, gameinfo and the stuff as strings.`
`04:38.37`	`EdmundEdmund`	`The server pick spawn is still there, although with a note`
`04:38.44`	`aMeatPopsicle`	`it shoudl be moved`
`04:38.57`	`aMeatPopsicle`	`unless you want to put in a server side state`
`04:39.05`	`aMeatPopsicle`	`I don't know why Mac didn't just movie it`
`04:40.10`	`EdmundEdmund`	`There is now an item to benchmark the BZDB requests which is supposed to be done before the release.`
`04:40.20`	`aMeatPopsicle`	`I see that`
`04:40.35`	`EdmundEdmund`	`That will probably be done by the same person who's doing the gameinfo`
`04:41.05`	`aMeatPopsicle`	`I'm moving the spawn thingy`
`04:41.22`	`EdmundEdmund`	`I'm updating the wipi`
`04:41.50`	`CIA`	`03jeffm2501 * 12bzflag/ (TODO): Moved server spawn calc to not release crit, as it's rather involved, don't think so, then get in here and spec it out.`
`04:43.01`	`EdmundEdmund`	`It would be nice if everything release critical had some spec to accompany it.`
`04:43.26`	`aMeatPopsicle`	`it would be nice if anything had a spec`
`04:43.27`	`aMeatPopsicle`	`or a note`
`04:43.33`	`aMeatPopsicle`	`or even a couple terse words`
`04:43.47`	`EdmundEdmund`	`Read the wipi, it's been getting a little bit of it.`
`04:44.03`	`aMeatPopsicle`	`yeah it has`
`04:44.09`	`aMeatPopsicle`	`but you know what I mean`
`04:44.29`	`EdmundEdmund`	`I've been updating the wipi, so I think I know exactly what you mean.`
`04:45.06`	`aMeatPopsicle`	`noone takes ownership of anything, and he who puts things on the "Crit" list dosn't seem to indicate what they want.`
`04:45.29`	`EdmundEdmund`	`The gameinfo request became much more complete a while back.`
`04:46.33`	`aMeatPopsicle`	`where is it defined what it should do?`
`04:46.40`	`EdmundEdmund`	`in the TODO`
`04:47.00`	`CIA`	`03brlcad * 12bzflag/src/bzfs (2 files): reworked the computation of poll "success"; added method to check if the poll is bound to fail with given known votes`
`04:47.14`	`aMeatPopsicle`	`how hard is it?`
`04:47.51`	`EdmundEdmund`	`I'm not sure. I think it was part of the net reorg discussion, which rapidly got out of control.`
`04:48.10`	`aMeatPopsicle`	`are there any services that are going to use it?`
`04:48.58`	`EdmundEdmund`	`It's not clear that it really changes anything or improves network usage.`
`04:49.02`	`aMeatPopsicle`	`cus the only way to test it would be to change ibot or some other utility to use it`
`04:49.23`	`aMeatPopsicle`	`it sounds like the game server does a feature the list server does`
`04:50.25`	`aMeatPopsicle`	`like for ibot or one of those web pages to get the player lists and stuff direclty from the server`
`04:50.31`	`aMeatPopsicle`	`and not have to "log in"`
`04:51.04`	`EdmundEdmund`	`And why would it be required before the next release...`
`04:51.11`	`aMeatPopsicle`	`that is my question`
`04:51.20`	`aMeatPopsicle`	`it dosn't even sound like a client would even use it`
`04:51.32`	`aMeatPopsicle`	`unless it's needed for lan server location`
`04:51.43`	`aMeatPopsicle`	`or is that still working via broadcast?`
`04:52.26`	`aMeatPopsicle`	`I say bump it to a "would be in 1.9 if it had more info"`
`04:52.58`	`EdmundEdmund`	`I haven't wandered through that code. I got quite discouraged from pursuing it during that meeting.`
`04:53.00`	`aMeatPopsicle`	`#1 is going to require some hagaling with the build system`
`04:53.25`	`aMeatPopsicle`	`I don't even know how I'm gonna get the build date in VC`
`04:53.49`	`aMeatPopsicle`	`I don't know much VB to script it.`
`04:53.50`	`EdmundEdmund`	`It shouldn't be a problem, we could just define it for the build systems that won't support it automatically.`
`04:55.01`	`aMeatPopsicle`	`so he wants major.minor.rev-source_with_a_date ?`
`04:56.35`	`EdmundEdmund`	`Yes, although there's a note that asks for more specification. I should try coding something up to see how hard it is to add to the mac. It won't go into the file info automatically.`
`04:57.03`	`aMeatPopsicle`	`do you guys use a hardcoded config.h as well?`
`04:57.25`	`EdmundEdmund`	`No, we're using autoconfig`
`04:57.32`	`aMeatPopsicle`	`ahhh`
`04:58.11`	`EdmundEdmund`	`I might be able to write a script which pulls the version out of config and puts it into the file info`
`04:58.34`	`aMeatPopsicle`	`well I am going to have my config define some macros with the strings`
`04:58.38`	`aMeatPopsicle`	`cus that's all I can do`
`04:58.51`	`aMeatPopsicle`	`I would make autoconf add them to the generated config.h`
`04:58.53`	`EdmundEdmund`	`That should be sufficient`
`04:59.08`	`aMeatPopsicle`	`and I'll make it build up a string using those macros`
`04:59.56`	`aMeatPopsicle`	`#define BZ_MAJOR_VERSION "1"`
`04:59.57`	`aMeatPopsicle`	`#define BZ_MINOR_VERSION "9"`
`04:59.57`	`aMeatPopsicle`	`#define BZ_REV "0"`
`04:59.57`	`aMeatPopsicle`	`#define BZ_BUILD_SOURCE VC"`
`04:59.57`	`aMeatPopsicle`	`#define BZ_BUILD_OS "W32"`
`04:59.57`	`aMeatPopsicle`	`#define BZ_BUILD_DATE "20030911"`
`05:00.02`	`aMeatPopsicle`	`that look good enough?`
`05:00.36`	`EdmundEdmund`	`I would say yes. Code it up and then we'll pass it through fearless leader.`
`05:00.59`	`aMeatPopsicle`	`well if I do this it WILL break all non windows builds till somone fixes the conf`
`05:01.12`	`aMeatPopsicle`	`be a nice insentive for them :)`
`05:02.17`	`EdmundEdmund`	`#ifndef STRING`
`05:02.24`	`EdmundEdmund`	`#define STRING undefined`
`05:02.27`	`EdmundEdmund`	`#endif`
`05:02.51`	`aMeatPopsicle`	`k`
`05:02.53`	`EdmundEdmund`	`That should be sufficient to unbreak the other builds if you're using the strings somewhere.`
`05:03.16`	`aMeatPopsicle`	`well I'm saying the code will use these STRINGS and they won't be there for linux`
`05:03.26`	`aMeatPopsicle`	`till somone fixes the generation of config.h`
`05:03.33`	`EdmundEdmund`	`The version will look awful, which is exactly what we want until someone goes through and fixes them.`
`05:03.36`	`*** part/#bzflag SGI (~SGI@bgp01138bgs.sothfd01.mi.comcast.net)`
`05:03.43`	`aMeatPopsicle`	`well it won't build`
`05:04.08`	`EdmundEdmund`	`If you add the definition, it should build.`
`05:04.17`	`aMeatPopsicle`	`where would I add the def?`
`05:04.26`	`aMeatPopsicle`	`it's suposed to go in config.h`
`05:04.36`	`aMeatPopsicle`	`but on linux config.h isn't in cvs, it's generated`
`05:04.41`	`*** join/#bzflag snyke (~snyke@eros.bingo-ev.de)`
`05:04.55`	`EdmundEdmund`	`I would add it to the files where they get used, with a note to remove them when fixed.`
`05:05.14`	`aMeatPopsicle`	`I would leave it busted and make them fix it :)`
`05:05.59`	`EdmundEdmund`	`We could add something quickly to configure.in to define things.`
`05:08.12`	`CIA`	`03brlcad * 12bzflag/src/bzfs (VotingArbiter.cxx): bleh, name typo`
`05:09.23`	`aMeatPopsicle`	`hmmm, it's also tied to the "protocoll" version`
`05:09.36`	`aMeatPopsicle`	`and that till uses the "1.9a" type thing`
`05:11.09`	`*** join/#bzflag NinjaSocks (~jeffm@adsl-64-172-197-72.dsl.lsan03.pacbell.net)`
`05:11.39`	`*** mode/#bzflag [+o Patlabor221] by ChanServ`
`05:11.56`	`Patlabor221`	`I don't know how well this is gonna work`
`05:13.16`	`Patlabor221`	`well crap all this is is how we store the internal verison number`
`05:13.51`	`Patlabor221`	`it's sent over the wire as a string.`
`05:14.36`	`EdmundEdmund`	`Yeah, but the string is something like 10901000`
`05:14.47`	`Patlabor221`	`no`
`05:15.06`	`EdmundEdmund`	`What string are we using now?`
`05:15.11`	`Patlabor221`	`the string sent over the wire for protocol is "BZFS1.9a`
`05:15.34`	`Patlabor221`	`we keep 2 other verison numbers`
`05:15.51`	`Patlabor221`	`a string for "1.9a0"`
`05:16.10`	`Patlabor221`	`and the 109010000 that is parsed out into 1.9.a0`
`05:16.12`	`EdmundEdmund`	`I didn't see where that one is used, although I saw the string`
`05:16.16`	`Patlabor221`	`how lame is that`
`05:16.36`	`EdmundEdmund`	`That's the one which is apparently used to print out the version string.`
`05:16.47`	`Patlabor221`	`we intermix using the string for protocoll and for real version number`
`05:16.54`	`Patlabor221`	`I'm gonna seperate them`
`05:17.19`	`Patlabor221`	`cus then there is also "ServerVersion"`
`05:17.27`	`Patlabor221`	`and that's a string 1.9a as well`
`05:17.42`	`Patlabor221`	`so basicly we have the verson number 3 times`
`05:17.56`	`Patlabor221`	`I will make version and protocoll seperate`
`05:18.02`	`Patlabor221`	`and leave protocoll 1.9a`
`05:18.17`	`Patlabor221`	`but make the app version 1.9.0`
`05:18.23`	`EdmundEdmund`	`4 if you count the mac file info. I'm not sure if windows has something similar.`
`05:19.09`	`Patlabor221`	`const char* constServerVersion = "BZFS109a";`
`05:20.00`	`Patlabor221`	`tho that is in BZFS.cxx`
`05:20.20`	`Patlabor221`	`I'm gonna make it use a BZFS_PROTOCOLL define for the 109a part`
`05:21.58`	`EdmundEdmund`	`It would be nice if it were built from the config defines`
`05:22.07`	`Patlabor221`	`yeah`
`05:22.13`	`Patlabor221`	`with this change it can be`
`05:22.37`	`Patlabor221`	`the config just defines BZ_PROTO_VERSION and then it's used to make the string`
`05:23.00`	`Patlabor221`	`tho it's a freaking const now, so I don't know how I can get the macro in there`
`05:23.22`	`Patlabor221`	`looks like it won't be const any more`
`05:25.35`	`EdmundEdmund`	`I'll have to play with the preprocessor a bit and see if I can convince it to create a const if things are evaluated at compile time.`
`05:25.52`	`Patlabor221`	`I think I'm just gonna replace it with a function in common`
`05:26.03`	`Patlabor221`	`GetServerProtoString()`
`05:26.15`	`Patlabor221`	`since it's used all over the pace`
`05:26.32`	`Patlabor221`	`and it's not defined in config, it's defined in protocoll.h`
`05:27.02`	`EdmundEdmund`	`Just so we can remember to change it in yet another place.`
`05:27.19`	`Patlabor221`	`no, the func will build it from the defines in config`
`05:27.27`	`Patlabor221`	`so change in one place`
`05:27.45`	`Patlabor221`	`change in the conf, and everyone gets it`
`05:28.10`	`EdmundEdmund`	`I meant current state as opposed to what it should be. I still think I can convince the preprocessor to build it for us from the defines.`
`05:28.23`	`Patlabor221`	`you can, but I can't`
`05:28.34`	`Patlabor221`	`and I don't think it should`
`05:28.36`	`Patlabor221`	`that's not the compilers job`
`05:29.02`	`EdmundEdmund`	`The compiler's job is to make my job easier. That's one of my issues with c++`
`05:29.42`	`Patlabor221`	`by making it a function it's all piped thur the same place, then if we have to change the way the data is sent later, it's a lot easyer`
`05:30.01`	`Patlabor221`	`instead of some wierd preprocesor thing`
`05:30.23`	`Patlabor221`	`basicly I would be puting it in an API`
`05:30.43`	`EdmundEdmund`	`Make it a function now. I doubt it gets used often enough to really make a difference.`
`05:31.03`	`Patlabor221`	`it will be pulling from a static string so it won't be slow`
`05:31.39`	`Patlabor221`	`techinaly windows wize I should be pulling the version from the VERS resource`
`05:32.00`	`EdmundEdmund`	`The weird preprocessor thing should be something easy to understand. If it isn't then the language/tools are the problem.`
`05:32.29`	`Patlabor221`	`it should`
`05:32.46`	`Patlabor221`	`but I don't like defining application things based on my tools`
`05:33.02`	`Patlabor221`	`cus you never know, there may be some wacky difrent tools out there later :)`
`05:33.37`	`EdmundEdmund`	`Unfortunately all application things have to be defined based on the tools. Compilers are like that. ;^)`
`05:33.56`	`Patlabor221`	`well yes, but you can minimise it`
`05:34.53`	`EdmundEdmund`	`Certain methods are known to work with more tools. It's still defined based on the tools.`
`05:35.03`	`Patlabor221`	`yes I agree`
`05:35.24`	`Patlabor221`	`I think I'm gonna put the main version number in a func too`
`05:35.36`	`Patlabor221`	`makes sense that it should be a common service`
`05:35.58`	`EdmundEdmund`	`And grabbing it from the VERS resource is the right thing to do on all platforms. We could put the method for grabbing it from the resource into the platform dependencies.`
`05:36.35`	`Patlabor221`	`yeah, so if I put it in a function now, when we want to do the resouces it's a lot easyer later`
`05:36.45`	`Patlabor221`	`since all you have to do is make these funcs call something in plat`
`05:36.52`	`EdmundEdmund`	`Agreed`
`05:37.55`	`Patlabor221`	`this how they like to do it?`
`05:37.56`	`Patlabor221`	`const char* getProtocolVersion();`
`05:37.56`	`Patlabor221`	`const char* getAppVerstion()`
`05:38.16`	`Patlabor221`	`and linux has version resources?`
`05:38.34`	`EdmundEdmund`	`linux doesn't have version resources, but we can fake that.`
`05:38.57`	`Patlabor221`	`fark, there is no common.cxx`
`05:39.11`	`Patlabor221`	`I chould cheeze and put it in global.cxx`
`05:42.13`	`EdmundEdmund`	`I'm not sure where is the best place to put it. global doesn't have any code so far.`
`05:43.16`	`EdmundEdmund`	`Maybe adding a version.cxx to the common directory is the way to go.`
`05:43.35`	`Patlabor221`	`I'm gonna test it in global.cxx`
`05:43.40`	`Patlabor221`	`if that works I'll add verison.`
`05:46.13`	`Patlabor221`	`ok so printed version strings would be "1.9.0-W32-VC-20030911`
`05:46.16`	`Patlabor221`	`how does that sound`
`05:46.42`	`Patlabor221`	`and for you it would be like "1.9.0-OSX-CVS-20030911"`
`05:47.09`	`Patlabor221`	`or maybe PB instead of CVS for project builder`
`05:47.23`	`EdmundEdmund`	`That sounds good to me. Pass it by fearless leader tomorrow, and I'll change things around for Mac this weekend.`
`05:47.52`	`Patlabor221`	`I'm gussing releases would say like REL instead of CVS or something`
`05:47.53`	`EdmundEdmund`	`I'm heading back to read tomorrow's proceedings. I'll talk to you tomorrow.`
`05:48.05`	`Patlabor221`	`see ya`
`05:48.11`	`EdmundEdmund`	`g'nite`
`06:06.04`	`learner`	`g'night`
`06:11.45`	`Patlabor221`	`well if this runs and connects then I think the string thing is done`
`06:27.02`	`Patlabor221`	`and fixes learners errors`
`06:27.45`	`CIA`	`03jeffm2501 * 12bzflag/ (18 files in 9 dirs): (log message trimmed)`
`06:27.46`	`CIA`	`changed internal version number from the odd set of numbers to a set of #defines that are renderd out to strings`
`06:27.47`	`CIA`	`All version strings are now processed thru functions in common.`
`06:27.47`	`CIA`	`Version strings now include OS, build souce, and build date.`
`06:27.48`	`CIA`	`NOTE`
`06:27.49`	`CIA`	`All platforms will need to change there configure system to add the folowing to there config.h if they want to build.`
`06:27.51`	`CIA`	`config.h needs to define the folowing.`
`06:28.39`	`Patlabor221`	`awww I think I broke CIA`
`06:29.18`	`Patlabor221`	`well caused enough damage for one night.`
`08:07.22`	`*** join/#bzflag mmu_man (~revol@81.250.4.225)`
`08:45.56`	`*** join/#bzflag darek (darek@belar.mtl.pl)`
`08:52.23`	`*** part/#bzflag darek (darek@belar.mtl.pl)`
`09:12.43`	`*** join/#bzflag MrCooper (~daenzer@dclient80-218-114-28.hispeed.ch)`
`09:48.59`	`*** join/#bzflag Sniper50 (~Sniper50@c-6b8c70d5.09-28-6c756e1.cust.bredbandsbolaget.se)`
`10:07.48`	`*** join/#bzflag KTL_ (~KTL@scotty.kulnet.kuleuven.ac.be)`
`10:12.59`	`*** join/#bzflag MrCooper (~daenzer@dclient80-218-114-28.hispeed.ch)`
`10:28.03`	`*** join/#bzflag Electric1lf (~david@CPE00a0cc23b80f-CM400049226055.cpe.net.cable.rogers.com)`
`10:35.21`	`*** join/#bzflag mmu_man (~revol@ALyon-209-1-36-225.w81-250.abo.wanadoo.fr)`
`10:52.29`	`*** join/#bzflag tea\|tree_ (~tea\|tree@pD9E969B5.dip.t-dialin.net)`
`10:53.52`	`KTL_`	`test`
`11:11.02`	`CIA`	`03chestal * 12bzflag/src/bzflag (playing.cxx): simplify region handling logic: use two moves instead of two swaps`
`11:13.18`	`dheckaman`	`mornin Chestal :)`
`11:36.37`	`fiberchunks`	`~convert 73.53 GBP to USD`
`11:36.58`	`fiberchunks`	`~convert 73.53 .uk to USD`
`11:37.08`	`fiberchunks`	`argh`
`12:10.01`	`learner`	`tag Chestal`
`12:10.34`	`learner`	`~sup G?`
`12:10.38`		`nuthin, yous?`
`12:10.53`	`learner`	`~change 73.53 GBP to USD`
`12:35.47`	`fiberchunks`	`ah`
`12:35.52`	`fiberchunks`	`duh`
`12:36.13`	`fiberchunks`	`is there some way to list all the commands and crap for ibot?`
`12:38.02`	`dheckaman`	`get the source and read it :P`
`12:38.14`	`dheckaman`	`<PROTECTED>`
`12:40.12`	`*** join/#bzflag larsl (~larsl@c213-100-62-55.swipnet.se)`
`12:42.34`	`larsl`	global.cxx:99: `BZ_PROTO_VERSION' undeclared (first use this function)
`12:42.42`	`larsl`	global.cxx:107: `BZ_MAJOR_VERSION' undeclared (first use this function)
`12:42.48`	`larsl`	global.cxx:107: `BZ_MINOR_VERSION' undeclared (first use this function)
`12:42.49`	`larsl`	`etc`
`12:43.38`	`dheckaman`	`wow`
`12:46.05`	`dheckaman`	`lol`
`12:55.04`	`*** join/#bzflag mmu (~revol@ALyon-209-1-29-107.w81-248.abo.wanadoo.fr)`
`12:56.43`	`tea\|tree_`	`http://starterupsteve.servepics.com:60000/swf/kozoFlash.html`
`12:56.47`	`tea\|tree_`	`;)`
`13:19.07`	`*** join/#bzflag scanline (~micah@home-dhcp5-247.Colorado.EDU)`
`13:23.13`	`*** join/#bzflag MrCooper (~daenzer@dclient80-218-114-28.hispeed.ch)`
`13:36.55`	`*** join/#bzflag Bagheera (~Bagheera@h-68-165-122-98.MCLNVA23.covad.net)`
`13:37.22`	`Bagheera`	`morn'in`
`13:38.09`	`*** join/#bzflag brlcad (sean@chr160dhcp1675.chrchv01.md.comcast.net)`
`13:43.25`	`*** join/#bzflag bryjen (~bryjen@63.147.94.145)`
`13:57.38`	`*** join/#bzflag TimRiker (~timr@proxyle02.ext.ti.com)`
`13:57.38`	`*** mode/#bzflag [+o TimRiker] by ChanServ`
`14:16.28`	`*** join/#bzflag Chikorita (Chikorita@AC989180.ipt.aol.com)`
`14:17.24`	`Chikorita`	`~d`
`14:18.12`	`Chikorita`	`~weather khgr`
`14:18.51`	`Chikorita`	`ibot: botsnack`
`14:18.51`		`thanks, Chikorita`
`14:18.58`	`Chikorita`	`yw`
`14:19.51`	`Chestal`	`~logs`
`14:19.51`		`http://ibot.rikers.org/<channelname>/, or stats http://ibot.rikers.org/stats/<channelname>.html.gz`
`14:22.42`	`dheckaman`	`20030911.html.bz in particular`
`14:23.00`	`dheckaman`	`search for bzdoug`
`14:23.02`	`dheckaman`	`gz*`
`14:41.25`	`dheckaman`	`hohoho :)`
`14:53.40`	`brlcad`	`hey, it's a dheckaman :)`
`14:53.57`	`dheckaman`	`doug jus sits`
`14:53.58`	`dheckaman`	`:P`
`14:54.20`	`dheckaman`	`and to think a few months ago he was complaining I talked too much`
`14:54.25`	`brlcad`	`hehe`
`14:54.42`	`brlcad`	`it was the molded cheesy beef that pat ate`
`14:54.52`	`brlcad`	`got him in a bad mood :)`
`14:54.53`	`dheckaman`	`ah`
`14:55.41`	`brlcad`	`you been away? that was like two/three days ago`
`14:56.17`	`dheckaman`	`no`
`14:56.19`	`dheckaman`	`busy`
`14:56.23`	`dheckaman`	`doing actual work`
`14:56.30`	`dheckaman`	`unlike some in here :)`
`14:59.33`	`brlcad`	`pfft! work? what's that?`
`15:01.18`	`dheckaman`	`yea, well, I like what I do... thus I can and play at the same time :)`
`15:01.49`	`brlcad`	`that's the way it should always be`
`15:06.13`	`*** join/#bzflag Bagheera (~Bagheera@h-68-165-122-98.MCLNVA23.covad.net)`
`15:10.15`	`*** join/#bzflag MrCooper (~daenzer@dclient80-218-114-28.hispeed.ch)`
`15:19.04`	`*** join/#bzflag MrCooper (~daenzer@dclient80-218-114-28.hispeed.ch)`
`15:34.43`	`*** join/#bzflag [dmp] (~dennis@D40A3023.rev.stofanet.dk)`
`15:38.21`	`ByeCash`	`howdy [dmp]`
`15:39.29`	`bryjen`	`<PROTECTED>`
`15:40.54`	`[dmp]`	`Hi Man with alot of names`
`15:41.38`	`*** join/#bzflag TyroneFHornigh (~JBDiGriz@p26.n-sfpop02.stsn.com)`
`15:43.48`	`bryjen`	`hrm. for some reason the name tyrone give me an image of a large, muscular, black man... i don't think i've ever known a tyrone tho...`
`16:01.02`	`TyroneFHornigh`	`How about a short hairy dirty old man leaning on a cane and sitting on a park bench. ;^)`
`16:01.15`	`*** join/#bzflag patlabor221 (~jeffm@208.48.199.214)`
`16:01.15`	`*** mode/#bzflag [+o patlabor221] by ChanServ`
`16:03.28`	`bryjen`	`nope`
`16:06.35`	`bryjen`	`http://display.lyrics.astraweb.com:2000/display.cgi?jethro_tull..aqualung..aqualung`
`16:08.04`	`bryjen`	`damnable pop-up ads!`
`16:08.14`	`bryjen`	`pfffft`
`16:15.11`	`tea\|tree_`	`~`
`16:15.14`	`tea\|tree_`	`~d`
`16:18.18`	`bryjen`	`Mmm TacoBell. Is it lunch time yet?`
`16:30.58`	`tea\|tree_`	`~d`
`16:33.07`	`*** join/#bzflag Big_Barrel (~chatzilla@adsl-64-219-214-108.dsl.hstntx.swbell.net)`
`16:35.36`	`bryjen`	global.cxx: In function `const char* getProtocolVersion()':
`16:35.38`	`bryjen`	global.cxx:99: `BZ_PROTO_VERSION' undeclared (first use this function)
`16:35.39`	`bryjen`	`...and others... half done?`
`16:37.26`	`patlabor221`	`read the commit message`
`16:37.35`	`patlabor221`	`and the dodo`
`16:37.38`	`patlabor221`	`and the bugs`
`16:37.57`	`patlabor221`	`autoconf needs the new version macros`
`16:39.00`	`bryjen`	`Just getting there...`
`16:39.11`	`CIA`	`03timriker 08v1_7 * 12bzflag/debian (control): new standards version`
`16:39.42`	`CIA`	`03timriker 08v1_7 * 12bzflag/ (2 files in 2 dirs): flatten symlinks`
`16:43.21`	`*** join/#bzflag TimRiker (~timr@proxyle01.ext.ti.com)`
`16:43.21`	`*** mode/#bzflag [+o TimRiker] by ChanServ`
`16:44.06`	`bryjen`	`Who's the auto-build-stuff guru?`
`16:44.14`	`bryjen`	`Tupone?`
`16:44.50`	`bryjen`	`~seen Tupone`
`16:44.51`		`tupone <~Tupone@ppp-217-133-255-186.cust-adsl.tiscali.it> was last seen on IRC in channel #bzflag, 17h 58m 16s ago, saying: 'Yeah, tomorrow'.`
`16:56.28`	`tea\|tree_`	`~d`
`16:56.55`	`*** join/#bzflag TimRiker (~timr@proxyle01.ext.ti.com)`
`16:57.18`	`*** mode/#bzflag [+o TimRiker] by ChanServ`
`16:57.20`	`patlabor221`	`I dono, I hooked up the one build system I know of, the DSP, JBD was gonna work on the mac stuff going.`
`17:00.30`	`*** join/#bzflag larsl (~larsl@c213-100-62-55.swipnet.se)`
`17:00.31`	`patlabor221`	`but it was on the release crit list so it had to be done.`
`17:05.28`	`*** join/#bzflag TimRiker (~timr@proxyle01.ext.ti.com)`
`17:05.57`	`*** mode/#bzflag [+o TimRiker] by ChanServ`
`17:11.08`	`ByeCash`	`bryjen: no -- definately a goodbye Cash..`
`17:11.41`	`patlabor221`	`where did you go?`
`17:12.02`	`ByeCash`	`Johnny Cash died`
`17:12.14`	`ByeCash`	`I went to lunch -- Chinese food :)`
`17:12.34`	`CIA`	`03jeffm2501 * 12bzflag/src/bzfls (bzfls.cxx): no need to use the server version and mod it when we have the proto version raw`
`17:12.38`	`patlabor221`	`John Ritter died too`
`17:12.47`	`ByeCash`	`yep`
`17:18.22`	`Bagheera`	`Why did Tennessee choose orange as their team color?`
`17:18.50`	`Bagheera`	`You can wear it to the game on Saturday, hunting on Sunday,and picking up trash along the highways the rest of the week.`
`17:24.07`	`*** join/#bzflag tea\|tree_ (~tea\|tree@pD9E96A5A.dip.t-dialin.net)`
`17:26.59`	`dheckaman`	`LOL`
`17:27.39`	`bryjen`	`Who's orange? (Besides the Cleveland _Browns_)`
`17:34.33`	`bryjen`	`ah, university of tennessee. hence the game on saturday.`
`17:44.40`	`patlabor221`	`hmm someone should check my functions in common to make sure they are ugly enough.`
`17:55.07`	`bryjen`	`They work?`
`17:59.27`	`patlabor221`	`they do work`
`17:59.46`	`bryjen`	`then "Meh, good enough" :)`
`17:59.59`	`patlabor221`	`I don't know how autoconf works so I could not add it there`
`18:00.12`	`TyroneFHornigh`	`I have a couple of quick definitions for configure.in which should allow compilations`
`18:00.17`	`patlabor221`	`but if you want you can use the calues from /win32/config.h`
`18:00.37`	`TyroneFHornigh`	`I haven't checked them in yet, and they need to be modified to get real definitions.`
`18:00.53`	`patlabor221`	`I tried to doc what was needed in the autoconf with my commit messages and comments, I hope it was enoguhg`
`18:01.19`	`ByeCash`	`Tyrone: definitions for configure.in, but not config.h.in?`
`18:02.06`	`ByeCash`	`pat: it's easy enough to add/fix`
`18:02.34`	`patlabor221`	`where would they be added? I'd like to know how this autoconf stuff works`
`18:03.25`	`ByeCash`	`can't get to that stuff right this second; when I get home I'll look at it if someone else doesn't beat me to it`
`18:03.45`	`TyroneFHornigh`	`config.h.in is generated automagically by autoconf from configure.in`
`18:04.11`	`patlabor221`	`so you don't have a config.h ?`
`18:04.23`	`patlabor221`	`or is config.h.in included by config.h ?`
`18:04.26`	`ByeCash`	`config.h is then generated off of the config.h.in template`
`18:04.31`	`TyroneFHornigh`	`I just added the following lines to configure.in after the VERSIONNUM`
`18:04.32`	`patlabor221`	`ahhhh`
`18:04.40`	`*** join/#bzflag KR (~k@cae168-234-054.sc.rr.com)`
`18:04.44`	`ByeCash`	`the ".in" files are templates`
`18:04.47`	`KR`	`how dee`
`18:04.50`	`TyroneFHornigh`	`Pardon the minor flood (7 lines)`
`18:05.08`	`ByeCash`	`configure.in is a template that autoconf uses to generate the configure script`
`18:05.43`	`ByeCash`	`didn't know config.h.in was autogen'd too though.... :)`
`18:05.56`	`TyroneFHornigh`	`AC_DEFINE(BZ_PROTO_VERSION, "109a", [Server Protocol version])]`
`18:05.56`	`TyroneFHornigh`	`AC_DEFINE_UNQUOTED(BZ_MAJOR_VERSION, 1, [Bzflag Major Version Number])`
`18:05.56`	`TyroneFHornigh`	`AC_DEFINE_UNQUOTED(BZ_MINOR_VERSION, 9, [Bzflag Minor Version Number])`
`18:05.56`	`TyroneFHornigh`	`AC_DEFINE_UNQUOTED(BZ_REV, 0, [Bzflag Revision Number])`
`18:05.56`	`TyroneFHornigh`	`AC_DEFINE(BZ_BUILD_SOURCE, "Undefined", [Bzflag Build Environment])]`
`18:05.57`	`TyroneFHornigh`	`AC_DEFINE(BZ_BUILD_OS, "Undefined", [Bzflag System Environment])]`
`18:05.59`	`TyroneFHornigh`	`AC_DEFINE(BZ_BUILD_DATE, 20039999, [Bzflag Build Date])]`
`18:10.53`	`KR`	`site with a built in inteligence detector http://www.nudelsalat.org/`
`18:11.49`	`ByeCash`	`KR: :)`
`18:12.17`	`KR`	`:)`
`18:13.45`	`TyroneFHornigh`	`Still compiling, and then I'll check it in. Note that the build environment and system environment need to be reworked so they get defined correctly later in the script.`
`18:14.47`	`ByeCash`	`Tyrone: what's wrong with those?`
`18:15.34`	`TyroneFHornigh`	`The date should be generated automatically. The build OS and environment should be determined and filled in correctly.`
`18:15.58`	`patlabor221`	`we don't need VERSIONNUM=10901000`
`18:16.03`	`patlabor221`	`do we anymore?`
`18:16.37`	`TyroneFHornigh`	`We should also verify that these changes still allow interaction between client and server. ;^)`
`18:16.46`	`patlabor221`	`they work fine`
`18:16.50`	`patlabor221`	`I tested last night`
`18:16.57`	`TimRiker`	`ok, whatcha changin'?`
`18:16.59`	`patlabor221`	`the server only looks for the 109a part`
`18:17.17`	`patlabor221`	`the item that was on the release list, make the version numbers strings.`
`18:17.20`	`TyroneFHornigh`	`VERSIONNUM is still being used to generate the string. We should replace that.`
`18:17.26`	`TimRiker`	`network version should be in int, like 3 perhaps.`
`18:17.26`	`patlabor221`	`and have the build date`
`18:17.36`	`TimRiker`	`no tie to the 1.9 etc release.`
`18:17.45`	`patlabor221`	`it is seperate yes`
`18:17.47`	`patlabor221`	`but it's a string`
`18:17.56`	`patlabor221`	`as that's what it did before`
`18:18.02`	`TyroneFHornigh`	`patlabor221: your changes work, but I'd like to verify that the above changes don't have a stupid mistake in them.`
`18:18.09`	`patlabor221`	`ahh`
`18:18.19`	`TimRiker`	`version string should not need to be parsed anywhere. Server might parse it, but does not need to.`
`18:18.30`	`patlabor221`	`it's not`
`18:18.33`	`larsl`	TyroneFHornigh: Would `date +%Y%m%d` work on all platforms for getting the date?
`18:18.38`	`patlabor221`	`it's just sent as a message`
`18:18.45`	`TimRiker`	`do we really need BZ_MAJOR_VERSION, BZ_MINOR_VERSION, BZ_REV, anywhere?`
`18:19.03`	`patlabor221`	`I figured that was easyer to change`
`18:19.10`	`patlabor221`	`it could be put into one var`
`18:19.14`	`TimRiker`	`larsl: well, not windows, but cygwin etc should be ok.`
`18:19.24`	`TyroneFHornigh`	`larsl: It would work for all unix platforms, but pat might need something different for win. I haven't figured out how to execute that from autoconf.`
`18:19.48`	`patlabor221`	`no mater what I have to do something funky on win, so don't worry about me`
`18:20.06`	`larsl`	`TyroneFHornigh: You just type the command. configure is just a shell script.`
`18:20.14`	`patlabor221`	`the macros are put into a string once in the new version get funcs`
`18:20.22`	`TimRiker`	`if windows does autoconf, then "time" is likely to be there too.`
`18:20.43`	`patlabor221`	`if it's using autoconf yeah`
`18:20.56`	`patlabor221`	`but if it's using that then it's not using the VC config.h`
`18:21.01`	`TyroneFHornigh`	`configure is generated from config.in, so there's a bit of interaction that I haven't done before. It's probably really easy.`
`18:21.41`	`patlabor221`	`Tim do you want me to combine the major, minor, and rev into one version macro string?`
`18:21.48`	`TyroneFHornigh`	`actually configure.in`
`18:21.54`	`ByeCash`	`it doesn't hurt to keep them separate`
`18:22.03`	`patlabor221`	`that's what I thought`
`18:22.16`	`larsl`	`But that's just m4 macro expansion, so the command should still be executed correctly.`
`18:22.17`	`patlabor221`	`we also used to use them to infer the procoll version, but I split that out`
`18:22.37`	`patlabor221`	`now proto verison is totaly seperate`
`18:23.08`	`TimRiker`	`patlabor221: as long as the code just uses the combined version number, it does not bother me if it's created in pieces.`
`18:23.30`	`patlabor221`	`yes the code that uses it just calls getAppVersion()`
`18:23.47`	`patlabor221`	`noone uses the #defines anymore`
`18:23.57`	`patlabor221`	`cept the version funcs`
`18:25.23`	`patlabor221`	`it would make converting the version number to a resouce easyer on platforms that are suposed to have them.`
`18:25.30`	`patlabor221`	`like Win and Mac`
`18:27.37`	`TyroneFHornigh`	`If someone would like to take those changes and make them better, that's fine with me. I'm not on a particularly fast machine right now, and I'm also distracted by some other things.`
`18:28.12`	`TyroneFHornigh`	`Alternately, if someone would like to buy me a 17" powerbook so I can do these things faster, I'm open to negotiation. ;^)`
`18:28.23`	`larsl`	`One for me too.`
`18:28.28`	`patlabor221`	`it is kinda cool to see the OS of the server now :)`
`18:28.58`	`KR`	`what address should I send them to? ;)`
`18:29.16`	`patlabor221`	`I can send you a powerbook 165 :)`
`18:29.38`	`ByeCash`	`the Mac's not so much of a problem, since we just make it run configure and use the config.h`
`18:29.53`	`TyroneFHornigh`	`Something faster than a 6 year old iBook would help :^P`
`18:30.07`	`patlabor221`	`you do know what a powerbook 165 is right?`
`18:30.35`	`*** join/#bzflag SGIa (~SGI@bgp01138bgs.sothfd01.mi.comcast.net)`
`18:30.49`	`SGIa`	`hi`
`18:30.55`	`TyroneFHornigh`	`As I recall it was a 680x0 machine, but I don't recall more than that.`
`18:31.05`	`KR`	`ehi`
`18:31.11`	`KR`	`its SGI`
`18:31.13`	`patlabor221`	`68020`
`18:31.24`	`patlabor221`	`at 33 mhz`
`18:31.35`	`SGI`	`~seen dtremenak`
`18:31.36`		`dtremenak <~DTRemenak@host-225-121.dialup.innercite.com> was last seen on IRC in channel #bzflag, 4d 19h 1m 29s ago, saying: 'then you could say SW doesn't affect shots, just the guidance system'.`
`18:31.37`	`patlabor221`	`it's got a whoping 12 megs of ram in it`
`18:32.15`	`SGI`	`hi KR`
`18:32.34`	`patlabor221`	`with a 640x400 4 bit grayscale screen`
`18:33.07`	`KR`	`how can you afford hardware like that? :)`
`18:33.36`	`SGI`	`$$$`
`18:34.08`	`patlabor221`	`sucker cost me 2 grand new`
`18:34.22`	`SGI`	`$$$$$$$`
`18:34.33`	`KR`	`lol - isn't funny what they cost and what they are worth a few years later :)`
`18:34.49`	`SGI`	`6 months later`
`18:35.20`	`TyroneFHornigh`	`That machine is a bit older than 3 years.`
`18:36.03`	`Bagheera`	`~dict sucker`
`18:36.39`	`SGI`	`money sucker`
`18:36.44`	`TyroneFHornigh`	`How about a 6 year old machine which is still running the latest OS, albeit a bit slow.`
`18:36.48`	`Bagheera`	`~dict 6 sucker`
`18:37.00`	`Bagheera`	`~dict 7 sucker`
`18:37.10`	`Bagheera`	`~dict 0 sucker`
`18:37.19`	`Bagheera`	`~dict 1 sucker`
`18:37.25`	`ByeCash`	`jeesh.. my sparcbook 2 from 10 years ago has better specs than that notebook ;)`
`18:37.40`	`Bagheera`	`~dict 2 sucker`
`18:37.51`	`SGI`	`~dict first sucker`
`18:38.31`	`SGI`	`no...first sucker ..wife goin out to buy with friends`
`18:38.50`	`patlabor221`	`yay, I have date and time macros in VC :)`
`18:39.41`	`SGI`	`i g2g`
`18:39.44`	`SGI`	`bye`
`18:43.00`	`CIA`	`03dbw192 * 12bzflag/ (configure.in):`
`18:43.00`	`CIA`	`Add defines to the autoconf so that builds will work again. These defines`
`18:43.01`	`CIA`	`need to be updated for real values.`
`18:43.55`	`TyroneFHornigh`	`I'm listening to a talk about supercomputer rocks.`
`18:45.40`	`ByeCash`	`supercomputers use rocks? :)`
`18:46.12`	`ByeCash`	`rocks that compute?`
`18:46.17`	`TyroneFHornigh`	`Deploying supercomputers around the volcanoes of Hawaii to take measurements.`
`18:46.47`	`TyroneFHornigh`	`They don't want people to walk off with them, and they need to survive the environment.`
`18:50.15`	`patlabor221`	`well if this works, windows will automaticly put the build date in there, and mark if it's release or debug`
`18:51.33`	`KR`	`apt-get uninstall lava`
`18:51.51`	`KR`	`:)`
`18:52.22`	`ByeCash`	`hrm.. ./configure: ]: command not found`
`18:54.25`	`TyroneFHornigh`	`Ack, there's a spare ']' after the BZ_PROTO_VERSION`
`18:54.54`	`ByeCash`	`i get 4 of those.. near make check -- looking`
`18:54.56`	`TyroneFHornigh`	`It doesn't affect the mac build. Could you try removing it and rebuilding?`
`18:55.24`	`larsl`	`BUILD_SOURCE,BUILD_OS, and BUILD_DATE too.`
`18:55.36`	`TyroneFHornigh`	`Yeah, it's after all of the UNQUOTED. Sorry about that.`
`18:56.05`	`larsl`	`It worked fine on Linux with autoconf 2.13 though.`
`18:56.36`	`TyroneFHornigh`	`Actually, try the date command on that as well. May as well get it working if we can.`
`18:57.09`	`larsl`	`Got it working.`
`18:57.36`	`TyroneFHornigh`	`Great. :^)`
`18:58.10`	`CIA`	`03brlcad * 12bzflag/ (configure.in): oopsie extraneous brackets`
`19:00.23`	`larsl`	`Was the date supposed to be a string or an int?`
`19:00.43`	`ByeCash`	`it's a literal ########`
`19:00.57`	`larsl`	`Oh, no " then.`
`19:01.01`	`ByeCash`	`yea`
`19:01.47`	`CIA`	`03larsl * 12bzflag/ (configure.in): Generate BZ_BUILD_DATE using Fri Sep 12 20:59:25 EDT 2003 in configure.in`
`19:03.09`	`larsl`	`Oops. =)`
`19:03.18`	`Bagheera`	`huh, computers camoflagued as rocks..........nice idea for a tank flag actually......hit a key and your tank looks like a pyramid....`
`19:03.23`	`larsl`	Maybe I shouldn't have backticked `date` in the message.
`19:03.53`	`ByeCash`	`lol`
`19:04.39`	`ByeCash`	`Bags: actually that is a cool idea, especially if radar matched :)`
`19:07.15`	`Bagheera`	`its different....thats for sure`
`19:10.21`	`Bagheera`	`would be funny to see a pyramid driving around the map..........guess it would only work if the tank was stationary....`
`19:11.03`	`ByeCash`	`yea, drive and you are a tank, stop and poof you morph into a pyramid`
`19:11.25`	`CIA`	`03larsl * 12bzflag/ (configure.in): Use the autoconf variable as BZ_BUILD_OS`
`19:11.46`	`larsl`	`Bleh, forgot substitution again.`
`19:11.57`	`larsl`	`cvs ci -m "Use the autoconf variable $host_os as BZ_BUILD_OS"`
`19:18.43`	`CIA`	`03larsl * 12bzflag/src/bzadmin (bzadmin.cxx): Fixed -help bug in bzadmin`
`19:19.06`	`TyroneFHornigh`	`I'm off the net for a couple of days until I get back home, cya.`
`19:19.14`	`Bagheera`	`cya`
`19:19.30`	`ByeCash`	`Cya guy`
`19:19.39`	`bryjen`	`later TFH`
`19:20.13`	`*** join/#bzflag david_v (~david_v@c213-200-135-241.cm-upc.chello.se)`
`19:22.17`	`bryjen`	`"BZFlag version 1.9.0-linux-gnu-Undefined20030912"`
`19:22.55`	`bryjen`	`perhaps BZ_BUILD_SOURCE should be set to CVS in CVS? ;) any maybe another - or two or something in there`
`19:23.39`	`ByeCash`	`What's that supposed to mean?`
`19:24.31`	`bryjen`	`ah, there is a - between gnu and Undefined. didn't see it at first`
`19:24.32`	`larsl`	`There probably should be a '-' between SOURCE and DATE.`
`19:25.30`	`larsl`	`And the SOURCE and DATE might not be needed at all if it is a release version.`
`19:25.42`	`ByeCash`	`but... what does it "mean"??`
`19:26.00`	`bryjen`	`ByeCash: see include/common.h`
`19:26.39`	`bryjen`	`or ask patlabor221`
`19:27.15`	`bryjen`	`but i can hear him saying "read include/common.h" already`
`19:27.48`	`ByeCash`	`sigh -- what is meant by "build environment"? visual studio/project builder/makefiles or cvs/downloaded or something else -- what information about the build environment is that supposed to be conveying?`
`19:29.09`	`larsl`	`"Build environment" is probably a bad description.`
`19:29.16`	`larsl`	`From common.h: #define BZ_BUILD_SOURCE"CVS"// what built it, CVS, RELEASE, TEST, ETC...`
`19:29.37`	`bryjen`	`eh, yeah. CVS doesn't build it ;)`
`19:29.55`	`ByeCash`	`ahh.. the commit message was helpful :)`
`19:30.06`	`ByeCash`	`my common.h does not have that comment...`
`19:30.29`	`larsl`	`Odd.`
`19:30.54`	`larsl`	`It's in a comment block at the end of the file in my version.`
`19:30.57`	`TimRiker`	`would be nice to do as mozilla/xchat etc do and report OS release at runtime.`
`19:31.10`	`TimRiker`	`-TimRiker- VERSION xchat 1.8.9 Linux 2.4.20-petfinal-6timr [i686/1794MHz]`
`19:31.34`	`larsl`	`uname -s -r ?`
`19:31.55`	`ByeCash`	`a BZ_BUILD_USER might be useful`
`19:34.39`	`bryjen`	`Including the OS in the program's version statement strikes me as odd. For a second I ask myself "is that the currently running info, or the OS version this was built on/for"`
`19:36.22`	`bryjen`	`maybe insert the words "running on" in there`
`19:36.55`	`larsl`	`Might not be running on that system, though. =)`
`19:37.08`	`larsl`	`Wine, Linux emulation in BSD etc.`
`19:38.32`	`bryjen`	`Ok. "using the api of" ;)`
`19:43.19`	`dheckaman`	`how about this: mac on wine on linux on x86 emulator on a mac on a windows computer?`
`19:43.28`	`larsl`	`Mac on Wine?`
`19:43.45`	`dheckaman`	`yea, basilisk II... even though they have a linux native version`
`19:43.45`	`bryjen`	`and mac on windows?`
`19:44.05`	`dheckaman`	`again, basilisk II on windows :)`
`19:44.17`	`bryjen`	`sigh`
`19:44.21`	`bryjen`	`~lart dheckaman`
`19:44.34`	`dheckaman`	`not a doohicky mouse cord!`
`19:44.48`	`KR`	`on a win ce kandheld :)`
`19:45.01`	`bryjen`	`careful, or ill break out the fireware. It Burns!`
`19:45.08`	`bryjen`	`s/fireware/firewire`
`19:45.24`	`dheckaman`	`eek`
`19:45.43`	`dheckaman`	`larsl: I did run system 7.6 on a pda...`
`19:52.55`	`CIA`	`03brlcad * 12bzflag/ (configure.in): better default BUILD_SOURCE..; added BZ_BUILD_USER to allow reporting who made a build`
`20:03.19`	`patlabor221`	`yeah I didn't know what to put there for the CVS thing`
`20:03.24`	`patlabor221`	`it was just shown in the example`
`20:03.39`	`patlabor221`	`so I put VCRelease or VCDebug in for windows.`
`20:05.43`	`ByeCash`	`i just set it to CVS since, well, it's all from cvs until RELEASE -- i figure the id can be used to track which branch of code the build came from (CVS, RELEASE, SOME_TEST, EXPERIMENTAL, etc)`
`20:05.59`	`captain_proton`	`...branch?`
`20:06.02`	`ByeCash`	`CVS implying HEAD`
`20:06.25`	`ByeCash`	`howdy cap`
`20:06.49`	`patlabor221`	`I dono, it wasn't really speficied what it was in the todo, so I just made a var for it`
`20:07.27`	`patlabor221`	`I don't think we wuld need the branch cus all branches are died to versions`
`20:07.41`	`patlabor221`	`I could see using it for Release, or a testing build.`
`20:07.47`	`patlabor221`	`but I don't know how to automate it.`
`20:07.58`	`ByeCash`	`I don't mean to actually create a proper cvs branch..`
`20:08.33`	`patlabor221`	`I wonder what Tim meant by it when he wrote it in the sample.`
`20:08.43`	`ByeCash`	`but yea.. when slapping together a build for the website -- you'd slap Release in there, or Beta, etc`
`20:09.08`	`*** join/#bzflag mmu_man (~revol@ALyon-209-1-29-107.w81-248.abo.wanadoo.fr)`
`20:09.31`	`patlabor221`	`I can see Release, testing, beta, and dev as tags`
`20:09.36`	`bryjen`	`an currently the end of the version # (e4 e6 g0 g2) implies a released single stable body of code`
`20:10.18`	`bryjen`	`there's only one g0 or g2 where there was a constantly changing g1`
`20:10.38`	`patlabor221`	`yeah`
`20:11.00`	`bryjen`	`that's not set in stone tho`
`20:11.06`	`patlabor221`	`what is?`
`20:11.22`	`bryjen`	`those commandment things...`
`20:12.35`	`Bagheera`	`grog...<cink, cink,cink>.....does here by.......<cink, cink, cink>........state the version......<cink, cink, cink, cink, cink>..........is g3...<cink,......>`
`20:12.46`	`Bagheera`	`ooooowwwww, the hammer slipped`
`20:13.18`	`patlabor221`	`that's the only thing I can think of`
`20:13.19`	`bryjen`	`do not try to read the mind of Go^W Tim`
`20:13.40`	`larsl`	`Is a tag really needed for the actual releases?`
`20:13.50`	`ByeCash`	`~envoke TimRiker`
`20:14.07`	`patlabor221`	`it may be nice to tag "testing" builds`
`20:14.18`	`patlabor221`	`ones that are sent out for mass testing`
`20:14.21`	`patlabor221`	`like on BZBB`
`20:15.07`	`bryjen`	`or if the verson numbering changes that you can't easily tell what's a release`
`20:16.04`	`patlabor221`	`well here we make sure that every real release has at least a new minor rev`
`20:16.10`	`patlabor221`	`sorry minor version`
`20:16.24`	`patlabor221`	`and we use the rev to designate the various sub builds as we dev`
`20:16.44`	`patlabor221`	`so right now we are making like 6.80.55 and that will become 7.0 later`
`20:16.47`	`ByeCash`	`yes, so you won't need keywords -- you should be able to derive it from the numbering`
`20:16.56`	`patlabor221`	`then we will do 7.01.xx to become 7.2`
`20:17.04`	`patlabor221`	`yeah`
`20:17.17`	`patlabor221`	`we seem to use the rev for releses`
`20:17.22`	`larsl`	`When do you increase the revision?`
`20:17.42`	`ByeCash`	`the keyword could be used to name releases, though.. MehItsGoodEnough :)`
`20:17.44`	`patlabor221`	`with each weekly build that is used for testing.`
`20:18.11`	`patlabor221`	`when bugs are reported they are reported to us with what specific revision was used for testing.`
`20:18.29`	`patlabor221`	`tho BZ does not do a centeral build system`
`20:18.38`	`patlabor221`	`we don't have "ofical" testing releases`
`20:19.01`	`patlabor221`	`if you want to test you are presently required to build.`
`20:19.20`	`bryjen`	`would NoItsCrap be the start of the development versions follwoing MehItsGoodEnough ? ;)`
`20:19.38`	`patlabor221`	`heh`
`20:20.02`	`patlabor221`	`my question to tim would be, what is the next release gonna be called? 1.9.0?`
`20:20.10`	`patlabor221`	`if so then we have to use that tag for sub lables`
`20:20.18`	`captain_proton`	`1.9.17 and a half`
`20:20.26`	`patlabor221`	`if it's gonna be 2.0 then we can use 1.9.x for sub versions.`
`20:20.39`	`ByeCash`	`1.9.17.0.5`
`20:20.50`	`patlabor221`	`1.9.17.1/2`
`20:20.54`	`bryjen`	`the current CVS as 1.9a0 kinda breaks the even=stable odd=devel pattern`
`20:21.14`	`captain_proton`	`we should make the version number approach i :)`
`20:21.26`	`ByeCash`	`No it doesn't.. you think it's stable??`
`20:21.30`	`bryjen`	`i ?`
`20:21.53`	`captain_proton`	`uhhuh`
`20:21.55`	`captain_proton`	`e & pi are used`
`20:21.57`	`bryjen`	`a0 = even, upping it by one at relase makes it a1 and 1 = odd`
`20:22.54`	`patlabor221`	`well it dosn't have an A in it anymore`
`20:23.01`	`patlabor221`	`the A is only in the protocoll version`
`20:23.10`	`ByeCash`	`Well.. going to triplet versioning would shift that up a notch, 1.9.0 implies first of an unstable, 2.0.0 would be the first stable`
`20:23.24`	`patlabor221`	`yeah, that's what I'm saying`
`20:23.25`	`captain_proton`	`we should make protocol version follow real version`
`20:23.34`	`larsl`	`Protocol = 1.9 ?`
`20:23.39`	`captain_proton`	`then leave it when the protocol remains stable`
`20:23.54`	`patlabor221`	`proto is now "109a" as a string`
`20:24.01`	`captain_proton`	`so protocol would be 1.9.0, and if it doesn't change, it could remain that while the version itself was 1.9.4 or whatnot`
`20:24.02`	`patlabor221`	`I left it the same for compatbility`
`20:24.02`	`bryjen`	`I think Tim suggested the current proto was # 3`
`20:24.11`	`patlabor221`	`but it's no longer tied to the app version`
`20:24.14`	`captain_proton`	`then update to match when the proto changes`
`20:24.23`	`patlabor221`	`that makes sense to me`
`20:24.26`	`Chestal`	`so every 2 days? :-)`
`20:24.37`	`patlabor221`	`so for this one we would make it "109"`
`20:24.44`	`bryjen`	`Chestal: so and int won't do?`
`20:24.50`	`bryjen`	`s/and/an`
`20:25.03`	`patlabor221`	`well if we used the rev for in dev changes then we could`
`20:25.15`	`patlabor221`	`the proto version is just a string, it can be anything`
`20:25.25`	`patlabor221`	`even "your mama is so fat.."`
`20:25.43`	`Chestal`	`I guess my question is whether it is a good idea to change the protocol version only for releases or everytime we make an incompatible version whiel developing`
`20:26.00`	`patlabor221`	`I think the proto should only change when the proto changes`
`20:26.12`	`patlabor221`	`but what you change it to when it does, is the same as the app version at that time.`
`20:26.36`	`patlabor221`	`but that would need incremented revs during dev`
`20:26.40`	`captain_proton`	`patlabor221: that works for releases, but doesn't notify us when MAC changes something`
`20:26.41`	`captain_proton`	`ya`
`20:26.53`	`patlabor221`	`it does if mac bumps the rev when he changes`
`20:27.00`	`patlabor221`	`the "a" don't cut it`
`20:27.07`	`captain_proton`	`i guess we could use a letter`
`20:27.15`	`captain_proton`	`1.9.0a b etc`
`20:27.16`	`patlabor221`	`why not use the rev?`
`20:27.29`	`patlabor221`	`we should be working on 1.9.x as we dev now`
`20:27.32`	`captain_proton`	`you mean the sub-minor version?`
`20:27.36`	`patlabor221`	`working tward ether 1.10 or 2.0`
`20:27.43`	`patlabor221`	`yeah, I call that the revision`
`20:27.50`	`captain_proton`	`so our protocol would be 1.9.65 or whatnot while the app would be 1.9.0?`
`20:27.58`	`ByeCash`	`it's easy enough to get something at least auto-increment a build-rev for the patch-level number`
`20:28.02`	`patlabor221`	`no the app would be 1.9.75`
`20:28.24`	`patlabor221`	`or what ever build you are on.`
`20:28.33`	`patlabor221`	`I don't know if I could automate that on windows, but maybe`
`20:28.47`	`patlabor221`	`I don't think it would have to be automated tho`
`20:28.50`	`tea\|tree_`	`uh`
`20:29.22`	`patlabor221`	`I would have it be somones job to do like a weekly build if there have been changes that bumps the rev`
`20:29.32`	`patlabor221`	`or you bump when there are decent changes.`
`20:29.38`	`patlabor221`	`revisions are cheap`
`20:30.00`	`patlabor221`	`then during testing when somone reports a bug we can know exactly what rev they are using`
`20:30.13`	`ByeCash`	`hrm, there should be a way to do it for windows too (automatically); I've seen vc6 apps do it`
`20:30.14`	`patlabor221`	`cus if they built themselves the date won't do us any good`
`20:30.22`	`patlabor221`	`I'm sure there is away`
`20:30.23`	`ByeCash`	`don't remember what they did, though :/`
`20:30.26`	`patlabor221`	`I just don't know it.`
`20:30.30`	`patlabor221`	`I can probably dig it up`
`20:30.38`	`patlabor221`	`I found the date and time stuff :)`
`20:30.41`	`*** join/#bzflag KTL (~KTL@scotty.kulnet.kuleuven.ac.be)`
`20:31.02`	`Chestal`	`hmm, the version date is build date or CVS date?`
`20:31.25`	`patlabor221`	`on windows I have it using the build date`
`20:31.29`	`patlabor221`	`cus that's all I got`
`20:31.59`	`*** join/#bzflag sn0w_m0nkey (~sn0w_m0nk@photon.health.unm.edu)`
`20:32.33`	`Chestal`	`I'm sure someone can apply some CVS magic which woudl autocreate a file with #define BZDATE ... on each commit`
`20:33.11`	`patlabor221`	`sure, but I think that is a minor issue compared to what is the "CVS" part and what to do about the revision`
`20:33.27`	`patlabor221`	`geting the date is an implmentation thing`
`20:33.51`	`Chestal`	`so we want subrevisions bewtween releases?`
`20:33.55`	`Chestal`	`thoguht the date coudl be used for that`
`20:34.13`	`patlabor221`	`then what is the sub version for?`
`20:34.16`	`Chestal`	`but of ourse we could auto-increment a subrevision on each commit`
`20:34.29`	`Chestal`	`like 1.90a.5673`
`20:34.38`	`Chestal`	`or whatever the current scheme is`
`20:34.43`	`patlabor221`	`the a is gone`
`20:34.53`	`patlabor221`	`so it would be 1.9.5673`
`20:34.54`	`Chestal`	`ok, then maybe 1.91.5673`
`20:35.00`	`Chestal`	`and release woudl be 1.92.0`
`20:35.18`	`ByeCash`	`cvs has a way to do that automatically to the source file on checkout`
`20:35.30`	`ByeCash`	`and updates, etc`
`20:35.55`	`bryjen`	`some different terms to clarify: MajorVer dot MinorVer dot RelaseNum dot CVScommitNum ?`
`20:35.57`	`patlabor221`	`that is why I ask, what does Tim want for the next rev?`
`20:36.30`	`patlabor221`	`if it's to be 1.9.0 then we should be working as 1.8.xxx`
`20:37.03`	`patlabor221`	`but at least I did the hard part, app, and proto version are sperated`
`20:37.14`	`patlabor221`	`so if we change now, it's just a change in one place and everyone gets it.`
`20:37.51`	`Chestal`	`hmm, we should first define what the next and future releases should be versioned as`
`20:37.58`	`patlabor221`	`yes`
`20:38.04`	`bryjen`	`so patlabor221 leans toward: Version . Release . Mod`
`20:38.09`	`patlabor221`	`yes`
`20:38.25`	`patlabor221`	`that is how a number of apps do it.`
`20:38.37`	`Chestal`	`then we shoudl start with 2.0.0 I guess`
`20:38.49`	`bryjen`	`Linuxish without the -per nonsense`
`20:39.01`	`bryjen`	`ugh. -preX`
`20:39.20`	`Chestal`	`so next release could be 2.0.0, release after that 2.1.0 and dev versions would be 2.0.1 upto 2.0.67584 whatever`
`20:39.55`	`bryjen`	`yup`
`20:41.08`	`Chestal`	`and proto version woudl only change if proto gets incompatibl and we could set it to game version then`
`20:41.38`	`bryjen`	`then releases are X.Y.0 and we're back to "what's BZ_BUILD_SOURCE for?"`
`20:41.39`	`ByeCash`	`Here we go: http://www.cvshome.org/docs/manual/current/cvs_12.html`
`20:42.10`	`ByeCash`	`You can snarf $Revision$ and use that wherever`
`20:42.11`	`Chestal`	`so, proto could be 2-0-0 for release, then we continue devleoping and at 2.0.875 we change protocol and then et proto version to 2-0-875 or soemthing similar`
`20:43.25`	`Chestal`	`ByeCash: hmm, yes, but this is per file?`
`20:43.31`	`ByeCash`	`yes`
`20:43.52`	`ByeCash`	`normally, you keep a static const in the file(s) that have a main (if not all of them)`
`20:55.27`	`ByeCash`	`e.g. static const char revision[] = "$Revision$"; // expands to "$Revision: 2.53 $" on commit`
`20:55.41`	`patlabor221`	`I added a set of fucntions in common to return the various version strings.`
`20:55.48`	`patlabor221`	`it pulls from the #defines now.`
`20:57.37`	`patlabor221`	`hmmm I don't know if I can get the build date in that format`
`20:58.02`	`purple_cow`	`hey look, donuts`
`20:58.21`	`patlabor221`	`it's giving me "Sep 12 2003" right now`
`20:58.34`	`patlabor221`	`guess I could parse out the Sep into a number`
`21:00.35`	`bryjen`	`<PROTECTED>`
`21:00.40`	`bryjen`	`whoops`
`21:00.52`	`bryjen`	`<PROTECTED>`
`21:03.03`	`*** join/#bzflag TyroneFHornigh (~JBDiGriz@66.151.148.200)`
`21:03.34`	`ByeCash`	`It's Tyrone! Thought you said you were going home?`
`21:04.01`	`TyroneFHornigh`	`I stopped by to have lunch with iluxa. He has to finish some work and has a wireless available.`
`21:05.13`	`TyroneFHornigh`	`Time to go, but it was fun saying hi!`
`21:05.40`	`ByeCash`	`hehe`
`21:06.29`	`Chestal`	`uh, all of a sudden I can no longer use /set to modify the globals. It says they are not writable?`
`21:07.05`	`CIA`	`03jeffm2501 * 12bzflag/win32 (config.h): VC version now uses build date automaticly, and designates between release and debug builds.`
`21:07.37`	`ByeCash`	`hrm.. Chestal: I added a check to bzdb to make sure the var is ReadWrite ..`
`21:07.52`	`ByeCash`	`er, not to bzdb but to the set func`
`21:07.55`	`patlabor221`	`you also broke windows builds las night :)`
`21:08.12`	`ByeCash`	`bah, that's what made it all worth it :)`
`21:08.47`	`Chestal`	`hmm, isn't there read only, server writable and client writable?`
`21:08.59`	`Chestal`	`and /set shoudl work on the latter two?`
`21:09.37`	`ByeCash`	`that would be the problem if true`
`21:09.59`	`Chestal`	`I'm not 100% sure, never look at the StateDatabase that close`
`21:10.24`	`ByeCash`	`there's a Permissions enum there`
`21:11.46`	`ByeCash`	`The enum has ReadWrite, Locked, ReadOnly, User, Server, and Client; the latter three are set to the first three`
`21:12.13`	`Chestal`	`uhm`
`21:12.48`	`purple_cow`	`why were User Server and Client added?`
`21:13.19`	`ByeCash`	`they are commented as "access levels", whereas the first three are "permissions levels"`
`21:13.31`	`purple_cow`	`but its the same thing`
`21:13.50`	`purple_cow`	`ReadWrite means the user can write (if we had a console like 1.9s...)`
`21:13.53`	`purple_cow`	`Locked means server can write`
`21:14.10`	`purple_cow`	`and ReadOnly means neither the user nor server can write (game-state type stuff)`
`21:14.27`	`Chestal`	`hmm, ok, I thin I get it, except for what 'CLient' means`
`21:14.44`	`purple_cow`	`Chestal: the readonly restriction is placed on the user, not the programmer`
`21:14.55`	`purple_cow`	`so the client itself can set those`
`21:14.58`	`purple_cow`	`just not the user of the client`
`21:15.02`	`Chestal`	`client can do everything?`
`21:15.06`	`purple_cow`	`yes`
`21:15.21`	`Chestal`	`k, then I guess those globals are set to Locked`
`21:15.41`	`Chestal`	`and as thus are server-changeable`
`21:16.09`	`purple_cow`	`right`
`21:16.33`	`tea\|tree_`	`~d`
`21:16.34`	`purple_cow`	`something like gravity is something you want the server able to write, but not the user`
`21:17.32`	`bryjen`	`Would things like soundvolume, brightness, geomtery be ReadWrite then ?`
`21:17.37`	`purple_cow`	`yes`
`21:17.50`	`Chestal`	`ByeCash: all is well when you remove that check I think,m bzdb->set does its own checking`
`21:18.19`	`ByeCash`	`Yes, it does do it's own checking, but set() doesn't return a helpful message back to the user`
`21:18.33`	`Chestal`	`hmm, what the heck is the CMDMGR?`
`21:18.42`	`bryjen`	`command manager?`
`21:18.47`	`patlabor221`	`yes`
`21:18.56`	`patlabor221`	`it maps keys to command events`
`21:18.57`	`tea\|tree_`	`hello`
`21:19.03`	`Chestal`	`ah, set has no return value, hmm`
`21:19.17`	`ByeCash`	`Otherwise you'd do /set sometingUnwriteable, and it'd say "sometingUnwriteable set" when it wasn't`
`21:19.32`	`patlabor221`	`hello`
`21:19.44`	`purple_cow`	`patlabor221: no, thats the KEYMGR`
`21:19.48`	`purple_cow`	`CMDMGR contains the command map`
`21:19.56`	`patlabor221`	`ahh`
`21:20.01`	`patlabor221`	`well they work togeher a lot :)`
`21:20.50`	`purple_cow`	`yes`
`21:21.00`	`purple_cow`	`win 5`
`21:21.02`	`purple_cow`	`err`
`21:21.12`	`purple_cow`	`CMDMGR is used to parse the config file, etc`
`21:22.04`	`ByeCash`	`is that beast documented anywhere?`
`21:22.18`	`purple_cow`	`CMDMGR? i believe the header is reasonably commented`
`21:22.22`	`ByeCash`	`I think I need to use his facilities for something else`
`21:22.24`	`Chestal`	`hmm, interesting`
`21:22.34`	`Chestal`	`so it could be used in the server for all the /comamnds maybe?`
`21:22.45`	`ByeCash`	`that's what I wanted to use it for`
`21:23.57`	`ByeCash`	`So what does it need, a function pointer and a text string?`
`21:24.44`	`purple_cow`	`to add a new command?`
`21:24.50`	`purple_cow`	`function pointer, name, & help string`
`21:24.51`	`ByeCash`	`yes`
`21:25.03`	`purple_cow`	`CommandManager::add`
`21:25.15`	`ByeCash`	`I assume CMDMGR is a singleton?`
`21:25.19`	`purple_cow`	`yup`
`21:25.35`	`ByeCash`	`what does is currently contain? key->command bindings?`
`21:25.54`	`purple_cow`	`pretty much`
`21:26.05`	`ByeCash`	`then what does KEYMGR contain?`
`21:26.08`	`purple_cow`	`it also handles parsing of commands into arguments`
`21:26.14`	`purple_cow`	`KEYMGR contains key->command mappings`
`21:26.30`	`ByeCash`	`how's that different?`
`21:27.03`	`bryjen`	`the .bzflag file has bind _command_ for CMNDMGR that setup the mappings`
`21:27.35`	`bryjen`	`commandS even.`
`21:28.40`	`ByeCash`	`Confusing, how do KEYMGR and CMDMGR differ?`
`21:29.14`	`patlabor221`	`dosn't key mananger get the key events?`
`21:29.27`	`patlabor221`	`and turn those into calls in the command mamanger?`
`21:30.10`	`ByeCash`	`Perhaps KEYMGR is key event -> command string mapping, whereas CMDMGR is command string -> function call mapping?`
`21:30.49`	`Chestal`	`uhm, how do I buidl bzadmin?`
`21:30.56`	`ByeCash`	`--enable-bzadmin`
`21:31.49`	`patlabor221`	`when I tracked that "i" problem I recall it going from platform->keymanager->commandmanager->thing that gets done`
`21:33.31`	`fiberchunks`	`whee! I just got my tablet, and all is well, as far as drivers and what not -- now to get X configured, and modules autoloading`
`21:33.32`	`ByeCash`	`mkay, that mostly makes sense, albeit those managers could probably be collapsed`
`21:33.51`	`purple_cow`	`ByeCash: KEYMGR is key->command`
`21:33.57`	`purple_cow`	`ByeCash: CMDMGR is command->implementation`
`21:34.28`	`purple_cow`	`ByeCash: well - each performs a different function`
`21:34.50`	`purple_cow`	`for example, CMDMGR is used when parsing the config - which doesn't involve keys at all`
`21:35.00`	`bryjen`	`and one of the CMDMGR commands is "bind", used to set KEYMGR's key->command mapping. kinda circular`
`21:35.18`	`purple_cow`	`circular, but sensical`
`21:35.41`	`ByeCash`	`circular is hardly ever a good thing in design ;)`
`21:35.42`	`Chestal`	`ah, there#s mult`
`21:35.51`	`Chestal`	`so I could add nifty keys for radar zooming this way`
`21:36.36`	`Chestal`	`like 'bind 4 down "mult displayRadarRange 0.95'`
`21:36.48`	`purple_cow`	`yup`
`21:36.57`	`ByeCash`	`but it sounds good, and I'm sure it's better than what was there so "cool deal" :)`
`21:37.37`	`Chestal`	`those zoomign keys work fine :-)`
`21:38.09`	`purple_cow`	`well - circular in this case works for me, because each piece does a very specific thing`
`21:38.50`	`ByeCash`	`how about "bind return '/poll kick Chestal'" ? :)`
`21:39.05`	`purple_cow`	`that wouldn't really work`
`21:39.18`	`ByeCash`	`hehe`
`21:39.21`	`purple_cow`	`but if you added a command to send something as a txt message, it would :)`
`21:39.44`	`purple_cow`	`"bind return send /poll kick Chestal`
`21:39.56`	`ByeCash`	`ah, cool`
`21:40.42`	`purple_cow`	`yay for stale doughnuts`
`21:40.59`	`ByeCash`	`how does the CMDMGR handle calling the function hook? more specifically, what is provided in terms of argument handling?`
`21:41.27`	`purple_cow`	`CMDMGR parses the string into args (using spaces & quotations)`
`21:41.38`	`Chestal`	`bind x "bind x fire" ;-)`
`21:41.40`	`purple_cow`	`then passes a vector of those`
`21:41.45`	`ByeCash`	`and passes an argc/argv?`
`21:42.27`	`purple_cow`	`typedef std::string (*CommandFunction)(const std::string& name, const ArgList&);`
`21:42.34`	`purple_cow`	`typedef std::vector<std::string> ArgList;`
`21:42.36`	`ByeCash`	`bind ha "bind ha"`
`21:43.14`	`*** join/#bzflag Bagheera (~Bagheera@h-68-165-122-98.MCLNVA23.covad.net)`
`21:43.24`	`Bagheera`	`<PROTECTED>`
`21:43.32`	`Bagheera`	`not again`
`21:43.34`	`ByeCash`	`oopsie :)`
`21:43.36`	`purple_cow`	`heh`
`21:43.38`	`Bagheera`	`dang it`
`21:43.43`	`Chestal`	`good thign we have the logs :-)`
`21:43.59`	`purple_cow`	`this land is made of mountains, this land is made of mud, this land has lots of everything, for me and elmer fudd`
`21:44.00`	`Bagheera`	`i need a beer`
`21:44.20`	`purple_cow`	`this land has lots of trousers, this land has lots of mousers, and pussy cats to eat them when the sun goes down`
`21:44.24`	`bryjen`	`maybe you could type that command in the network tab instead of the channel tab`
`21:44.30`	`ByeCash`	`hehe :)`
`21:44.31`	`*** join/#bzflag Bagheera (~Bagheera@h-68-165-122-98.MCLNVA23.covad.net)`
`21:44.49`	`Bagheera`	`a beer would be better`
`21:45.15`	`ByeCash`	`it helps to not put a space in front of the slash too :)`
`21:45.39`	`Bagheera`	`bunch of wise as***s eh`
`21:45.49`	`bryjen`	`yeah, but if you put a space in there on the network tab, it doesn't send it as a message to the channel`
`21:45.51`	`Bagheera`	`i really need a beer`
`21:45.52`	`sn0w_m0nkey`	`someone said beer`
`21:46.02`	`Bagheera`	`you buying?`
`21:46.09`	`sn0w_m0nkey`	`20 mimnutes i will`
`21:46.19`	`sn0w_m0nkey`	`first round on me`
`21:46.21`	`ByeCash`	`I'll buy, come on up`
`21:46.23`	`bryjen`	`~dict mimnutes`
`21:46.37`	`sn0w_m0nkey`	`heh`
`21:46.55`	`sn0w_m0nkey`	`not since last night`
`21:47.06`	`bryjen`	`slurred typing and all ;)`
`21:47.14`	`sn0w_m0nkey`	`hehe`
`21:47.15`	`Bagheera`	`nah, just finished up a new map....tired eyes`
`21:47.53`	`ByeCash`	`oh, to see?`
`21:48.27`	`sn0w_m0nkey`	`does anyone know if hashmark server is gone for good?`
`21:48.35`	`Bagheera`	`its not eggs`
`21:48.46`	`Bagheera`	`its HeadAche.....hahhaa`
`21:49.06`	`Bagheera`	`but the quol version of eggs is up there as well`
`21:49.24`	`Bagheera`	`not me`
`21:49.53`	`Bagheera`	`ooka ooka`
`21:51.38`	`Bagheera`	`night cash, enjoy the rain`
`21:52.08`	`ByeCash`	`yep, thx`
`21:52.41`	`*** join/#bzflag Noodleman (~tuckerm@procyon.noodleroni.com)`
`21:53.16`	`Bagheera`	`"till the cows come home"... haha hahahahaha......hahahahhhahahahahahahahha`
`21:56.58`	`sn0w_m0nkey`	`does anyone know if hashmark server is gone for good?`
`21:57.24`	`purple_cow`	`sn0w_m0nkey: if they did, they would have answered the last 15 times you asked`
`21:57.38`	`sn0w_m0nkey`	`3rd time`
`21:57.46`	`sn0w_m0nkey`	`does anyone know if hashmark server is gone for good?`
`21:57.50`	`sn0w_m0nkey`	`thats the 4th`
`21:58.29`	`sn0w_m0nkey`	`thats too bad, that had a killer connection`
`21:58.51`	`Bagheera`	`try one of quols.......200mb.......`
`21:59.30`	`sn0w_m0nkey`	`quols is good from my house`
`21:59.52`	`sn0w_m0nkey`	`nobody likes to play speed server setups anymore :(`
`22:00.31`	`Chestal`	`with 1.9 peopel can setup servers that have higher tank speed by default`
`22:00.43`	`Chestal`	`and there is a 1.9 hashmark, but that won#t help you very much right now`
`22:00.44`	`sn0w_m0nkey`	`?`
`22:01.03`	`Chestal`	`a lot of the game parameters are settable on the server in 1.9`
`22:01.04`	`*** part/#bzflag Noodleman (~tuckerm@procyon.noodleroni.com)`
`22:01.05`	`sn0w_m0nkey`	`so no more need for all highspeed flags eh`
`22:01.10`	`sn0w_m0nkey`	`cool deal`
`22:01.15`	`Chestal`	`includign tank and shot speeds, gravity etc.`
`22:01.29`	`sn0w_m0nkey`	`awesome`
`22:01.37`	`sn0w_m0nkey`	`i look forward to this release`
`22:01.41`	`sn0w_m0nkey`	`hint hint`
`22:01.47`	`Chestal`	`I like to increase the gravity, makes for tiny little hops :-)`
`22:01.52`	`sn0w_m0nkey`	`yeah`
`22:01.57`	`larsl`	`Chestal: Can we set negative gravity?`
`22:02.09`	`Chestal`	`larsl: well, it is negative by default`
`22:02.15`	`larsl`	`OK, positive then.`
`22:02.18`	`sn0w_m0nkey`	`negative?`
`22:02.24`	`Chestal`	`larsl: when you set it to >0 weird things are about to happen I guess :-9`
`22:02.26`	`purple_cow`	`-9.8`
`22:02.32`	`sn0w_m0nkey`	`you mean jump off the planet?`
`22:03.24`	`Chestal`	`once in the air your z velocity would increase endlessly`
`22:03.38`	`sn0w_m0nkey`	`i think that happened to me in college`
`22:03.54`	`sn0w_m0nkey`	`listening to jimi hendrix in the desert`
`22:04.07`	`Chestal`	`hmm, how did you ever come down again?`
`22:04.14`	`sn0w_m0nkey`	`no :)`
`22:05.01`	`Chestal`	`my PC is definitely too slow by a factor of 100 or so`
`22:05.22`	`sn0w_m0nkey`	`your running less than 1gig?`
`22:05.59`	`Chestal`	`700MHz, 2x500MHz resp.`
`22:06.29`	`sn0w_m0nkey`	`sounds hot-rod`
`22:06.35`	`sn0w_m0nkey`	`supercharged`
`22:06.48`	`larsl`	`We could add flags that change the parameters.`
`22:06.58`	`Chestal`	`oh, bzadmin doesn't compiel here`
`22:07.03`	`larsl`	`Low gravity flag, slow shot flag etc.`
`22:07.31`	`larsl`	`Chestal: Do you get an error message?`
`22:08.24`	`Chestal`	`yes, a multipel defintion, still trying to sort that out`
`22:08.43`	`*** join/#bzflag Chikorita (Chikorita@AC823158.ipt.aol.com)`
`22:09.08`	`sn0w_m0nkey`	`hi chik`
`22:09.34`	`Chikorita`	`hi m0nkeyy`
`22:11.31`	`Chikorita`	`hey hey itz da monkeys , aint no monkeyin around , were too bizzy playin , 2 let anybody down...`
`22:11.34`	`Chikorita`	`heehe`
`22:12.11`	`sn0w_m0nkey`	`man thats an old song`
`22:12.28`	`Chikorita`	`heehe ya buh i used ta watch da show on MTV`
`22:12.34`	`sn0w_m0nkey`	`like from when i was a young -un`
`22:12.35`	`Chestal`	`hmm, that looks strange`
`22:12.39`	`Chikorita`	`davy was cute`
`22:12.46`	`sn0w_m0nkey`	`ew`
`22:12.51`	`Chestal`	`I'm not very familiar with complex templates, but I don't think this makes any sense`
`22:13.06`	`Chikorita`	`hmm`
`22:13.13`	`sn0w_m0nkey`	`we need a TRL server`
`22:13.20`	`Chikorita`	`lol sm`
`22:13.41`	`Chestal`	`larsl: the problem is int OptionParser::VariableParser<string>::parse(char** argv) (and <bool>)`
`22:13.50`	`Chestal`	`it's a redefinition`
`22:13.55`	`sn0w_m0nkey`	`have a good weekend everyone, blast you later!`
`22:14.01`	`Chikorita`	`byez sm`
`22:15.08`	`Chikorita`	`~d`
`22:15.29`	`*** join/#bzflag larsl (~larsl@c213-100-62-55.swipnet.se)`
`22:15.57`	`Chestal`	`larsl: did you get the problem?`
`22:16.57`	`larsl`	`No, BZFlag crashed my computer.`
`22:17.01`	`larsl`	`What was the problem?`
`22:18.28`	`Chestal`	`larsl: the problem is int OptionParser::VariableParser<string>::parse(char** argv) (and <bool>)`
`22:18.51`	`Chestal`	`when I get this right, you#re trying a specialization for string and bool`
`22:19.05`	`Chestal`	`but the class is the template, not the parse() member function`
`22:19.29`	`larsl`	`Ah.`
`22:19.41`	`larsl`	`So I need to make a specialization for the whole class?`
`22:20.27`	`Chestal`	`I guess so`
`22:20.38`	`larsl`	`What compiler did you use?`
`22:20.39`	`*** join/#bzflag patlabor221 (~jeffm@208.48.199.214)`
`22:20.39`	`*** mode/#bzflag [+o patlabor221] by ChanServ`
`22:20.44`	`Chestal`	`your compiler is eating that?`
`22:20.54`	`larsl`	`Yes, it's been working fine.`
`22:21.02`	`larsl`	`gcc 3.2.2`
`22:21.16`	`Chestal`	`3.3.2 here`
`22:21.22`	`patlabor221`	`wheee, I now have the latest version of DirectEvil`
`22:37.40`	`*** join/#bzflag Chikorita (Chikorita@AC823158.ipt.aol.com)`
`22:37.47`	`Chikorita`	`sowee im back`
`22:37.59`	`CIA`	`03larsl * 12bzflag/src/bzadmin (OptionParser.h): GCC 3.3 seems to want specializations for the whole template class, not just for member functions`
`22:38.17`	`Chikorita`	`i saw sum1 playin wif BZflag version 1.7g3`
`22:38.18`	`larsl`	`Chestal: Can you test that?`
`22:38.25`	`Chikorita`	`wut iz 1.7g3?`
`22:38.49`	`larsl`	`Chikorita: 1.7g2 with some bugfixes.`
`22:38.55`	`Chikorita`	`ooH`
`22:38.57`	`larsl`	`It hasn't really been released.`
`22:39.01`	`Chikorita`	`i c`
`22:39.07`	`Chikorita`	`k`
`22:39.27`	`Chikorita`	`ya i was a lil surprised 2 c it`
`22:39.44`	`Chikorita`	`wut OS iz dat 4?`
`22:39.56`	`Chikorita`	`j/w`
`22:39.57`	`larsl`	`Any OS. It's just code in CVS.`
`22:40.02`	`Chikorita`	`o okies`
`22:46.29`	`Chestal`	`larsl: compiles fine now`
`22:50.58`	`captain_proton`	`2 tak?`
`22:54.30`	`patlabor221`	`learn to talk`
`23:04.21`	`patlabor221`	`Tim what is the next version number going to be? 1.9.0 ? 1.10.0 or 2.0 ?`
`23:04.49`	`patlabor221`	`or 1.9.2?`
`23:06.52`	`tea\|tree_`	`ZzZzZzzZz..`
`23:11.29`	`*** join/#bzflag Spiff (Spiff@12-222-147-141.client.insightBB.com)`
`23:12.54`	`tea\|tree_`	`hey`
`23:13.14`	`Spiff`	`Hi TeA. :-)`
`23:20.04`	`larsl`	`Chestal: Great, thanks.`
`23:22.29`	`*** join/#bzflag bryjen (bryjen@ky-owensboro1a-242.owboky.adelphia.net)`
`23:28.14`	`TimRiker`	`patlabor221: 1.9.something`
`23:29.38`	`patlabor221`	`do you want the date to be CVS date or build date? build date makes sense to me, as CVS date makes no sense cus there are multiple files`
`23:30.15`	`patlabor221`	`I've got windows using the build date now automaticly.`
`23:30.46`	`*** join/#bzflag Tupone (~Tupone@ppp-217-133-255-186.cust-adsl.tiscali.it)`
`23:30.59`	`CIA`	`03timriker * 12bzflag/ (TODO): whitespace`
`23:31.43`	`patlabor221`	`and what is the intended meaning of the "CVS" part of the sample version shown? CVS for dev versions, and "release" for ofical builds, and the like?`
`23:32.30`	`TimRiker`	`build data makes sense to me too. need to insure that get's touched for each build then.`
`23:32.53`	`TimRiker`	`what source actually includes the date? need to rebuild that all the time I guess.`
`23:32.56`	`patlabor221`	`on windows I have it using a compiler macro that returns the date when the compiler is run`
`23:33.16`	`TimRiker`	`and you force that file to be recompiled?`
`23:34.25`	`patlabor221`	`yeah`
`23:34.36`	`patlabor221`	`it's generated on each compile`
`23:34.50`	`patlabor221`	`cus it actualy calls a function that generates it`
`23:35.37`	`patlabor221`	`since windows didn't give it to me in the format you wanted :(`
`23:36.21`	`larsl`	`On systems using autotools the date only changes when you run configure (now).`
`23:36.35`	`patlabor221`	`interesting`
`23:37.05`	`patlabor221`	`well I think then I have the basiscs of what you wanted, implmented in the code, just need to clean up autotools then.`
`23:37.32`	`patlabor221`	`I'm used to using the revision for each testing build`
`23:37.51`	`patlabor221`	`so if this was our product the next version would be 1.10 or 2.0`
`23:38.08`	`patlabor221`	`and dev versions would be 1.9.xx`
`23:38.36`	`patlabor221`	`but since we don't do like weekly builds or anythig here I can see how it would not make sense.`
`23:39.24`	`patlabor221`	`tho weekly dev builds would be cool :)`
`23:39.26`	`Chestal`	`larsl: is bzadmin already adjusted for 1.9?`
`23:40.03`	`larsl`	`Chestal: It works with the current protocol.`
`23:40.27`	`larsl`	`It doesn't autocomplete all new commands, but that's easy to add.`
`23:41.06`	`patlabor221`	`hmm, now if I could just get the installer to pull the version info from the same place`
`23:42.23`	`Chestal`	`larsl: I noticed that it uses 1.7 observer style, i.e. use @callsign`
`23:42.31`	`Chestal`	`larsl: Observer are now a special team in 1.9`
`23:42.47`	`larsl`	`Ah, didn't know that.`
`23:45.02`	`larsl`	`Should it be TankPlayer or ComputerPlayer?`
`23:45.30`	`Tupone`	`It is a Team not a type`
`23:45.44`	`larsl`	`Yes, but should it be TankPlayer or ComputerPlayer?`
`23:45.55`	`Tupone`	`TankPlayer`
`23:46.06`	`Tupone`	`ComputerPlayer are Robot -solo`
`23:47.18`	`*** join/#bzflag ElectricElf (david@electricelf.usercloak.freenode)`
`23:47.39`	`larsl`	`[ll@gnorf bzflag]$ src/bzfs/bzfs -c`
`23:47.45`	`larsl`	`Something failed`
`23:47.50`	`larsl`	`How useful. =)`
`23:48.04`	`TimRiker`	`larsl: used to be it didn't even say that much.`
`23:48.29`	`TimRiker`	`probably can't bind to the port or similar.`
`23:49.01`	`larsl`	`Makes sense, I already had one running in the background.`
`23:49.02`	`TimRiker`	`date != version.`
`23:49.38`	`TimRiker`	`the "version string" should include the version as well as the date compiled. if you ignore the date portion, then you do have the version.`
`23:50.21`	`TimRiker`	`but we are not likely to change the version every time recommit any change to any other file in cvs, so having the date is useful for indicating when the cvs checkout might have been done.`
`23:51.08`	`Tupone`	`We could have some freezing any minor release, or any night, and put sources in a tarball, with date-version inside`
`23:51.10`	`patlabor221`	`all the versions that are oputput in messages and strings have the date, all the versions that are sent over the wire don't`
`23:51.26`	`Tupone`	`The build generated will be comparable`
`23:51.57`	`Tupone`	`If you take from CVS you'll get a not comparable version.`
`23:52.04`	`patlabor221`	`no no no`
`23:52.09`	`TimRiker`	`patlabor221: versions sent over the wire for logging and admin purposes should have date, os, etc.`
`23:52.17`	`CIA`	`03chestal * 12bzflag/src/bzflag (playing.cxx): use the == for strings`
`23:52.21`	`patlabor221`	`yes they do, the ones that are for humans`
`23:52.31`	`TimRiker`	`patlabor221: k`
`23:52.42`	`patlabor221`	`tupone, protocoll version is seperate now, it has no date, so they are allways compatable.`
`23:53.10`	`patlabor221`	`it's kinda cool to see the server OS now when you login`
`23:53.19`	`TimRiker`	`Tupone: and if you compile with a different compiler you get a not comparable version.`
`23:53.49`	`patlabor221`	`but only in the human readable version codes, it's just to help report bugs.`
`23:54.19`	`patlabor221`	`makes it a lot easyer.`
`23:55.09`	`Tupone`	`I'm thinking about bug. If I generate a version with the day-time, how can I compare with another version with different datetime. They are equal or not? Depends on the time I generate`
`23:55.36`	`patlabor221`	`it's just day not time as well`
`23:55.49`	`patlabor221`	`and what do you mean "compare"`
`23:56.09`	`TimRiker`	`[SERVER->] BZFlag server 1.9.0-linux-gnu-CVS20030912, http://BZFlag.org/`
`23:56.09`	`TimRiker`	`HiX 2.0 running current CVS Tim@Rikers.org (20030912-18:01:36)`
`23:56.11`	`TimRiker`	`cool.`
`23:56.11`	`Tupone`	`Same behaviour, why you want to get date on the version`
`23:56.17`	`CIA`	`03larsl * 12bzflag/ (2 files in 2 dirs): BZAdmin now joins as a proper observer without adding '@' to the callsign, removed -team option, updated man page`
`23:56.37`	`patlabor221`	`if you get a bug report that says it uses a build on 2003,09,12 you can know that the code it was based on came on or before that day`
`23:56.38`	`TimRiker`	`Tupone: where tou see the 20030912, you would remove that.`
`23:57.17`	`Tupone`	`I just say, not build time but extraction time (could be)`
`23:57.30`	`patlabor221`	`extration?`
`23:57.35`	`Tupone`	`co`
`23:57.44`	`Tupone`	`cvs update`
`23:57.50`	`TimRiker`	`Tupone: it's not the version. it's the date. the version is 1.9.0. the os is linux-gnu. it's from CVS. it's build on 20030912`
`23:58.01`	`patlabor221`	`I would prefer build`
`23:58.18`	`patlabor221`	`cus I may make multiple test builds off the same CO`
`23:58.26`	`patlabor221`	`before I commit`
`23:58.38`	`patlabor221`	`with a CO they would all have the same date`
`23:58.51`	`patlabor221`	`with a build date I can know what one I am using.`

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.