IRC log for #bzflag on 20150920

01:14.06*** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu)
07:11.54*** join/#bzflag Notify (~notify@66-118-151-70.static.sagonet.net)
08:29.31*** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu)
10:55.02blast007Constitution: the Xcode project does seem to list at least the nagware config and a 'plugins.cfg' for one of the other two plugins that had a config (either superUser or serverControl), so you'd need to update those as well, and for consistency, either have none of them or all of them list the configs.  I'll be renaming the 'crontab' file to bzfscron.cfg, which is also referenced in the Xcode project.
11:04.32blast007BulletCatcher: where are you seeing a 10-line limit for -helpmsg?  Looks like it should grab the first 50 lines up to ~128 chars per line: https://github.com/BZFlag-Dev/bzflag/blob/2.4/src/bzfs/CmdLineOptions.cxx#L752
12:20.45*** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu)
14:06.56*** join/#bzflag ploosma (~ploosma@184-96-194-251.hlrn.qwest.net)
14:39.36*** join/#bzflag Notify (~notify@66-118-151-70.static.sagonet.net)
14:47.00*** join/#bzflag BZnotify (~BZnotify@192.30.252.46)
14:47.00BZnotify[13bzflag] 15blast007 pushed 3 new commits to 062.4: 02http://git.io/vnc1m
14:47.00BZnotify13bzflag/062.4 14e64d52d 15Scott Wichser: Remove a couple references to non-existent ReadMe.txt files.
14:47.00BZnotify13bzflag/062.4 14285b006 15Scott Wichser: Build the superUser plugin on Windows.
14:47.00BZnotify13bzflag/062.4 14f57f2b3 15Scott Wichser: Rename the bzfscron sample configuration file.
14:47.00*** part/#bzflag BZnotify (~BZnotify@192.30.252.46)
14:50.01*** join/#bzflag BZnotify (~BZnotify@192.30.252.46)
14:50.01BZnotify[13bzflag] 15JMakey pushed 1 new commit to 062.4: 02http://git.io/vnc1d
14:50.01BZnotify13bzflag/062.4 141172a79 15Jeff Makey: Update the bzfs -helpmsg man page entry to show the 50 line limit that has existed since r12449.
14:50.01*** part/#bzflag BZnotify (~BZnotify@192.30.252.46)
14:50.53BulletCatcherThat's what I get for believing the documentation.
14:52.52blast007:D
14:54.11BulletCatcherThe limit was 20 lines before r12449, so the man page was always wrong about that.
14:54.21blast007heh
14:54.44blast007"I'm thinking of a number from 1 to 10"  "20?"
14:54.50BulletCatcherlol
15:04.50blast007regarding the using the git hash as part of the version string, how will we get the hash when we're not using a git checkout?  for instance, from our source tar/zip.
15:06.57blast007Not finding any information about if it's possible for github's automatically generated source archives to have the hash embedded.
15:16.39blast007perhaps this?  https://web.archive.org/web/20150421011209/http://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#Keyword-Expansion
17:14.29*** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu)
18:07.31Constitutionmaybe "make dist" can dump it in a file?
18:14.05blast007so we'll have to run 'make dist' before every commit?
18:19.36Constitutionno, that would be secondary if it isn't a git repo
18:19.57Constitutionif it is a git repo, it could be extracted from that, presumably
18:51.49blast007or would it be better to just show 'unknown' if it's not a git repo?
19:24.45ConstitutionI'm presuming release binaries would be built from the make dist tarballs, so that would mean all of our release binaries would show unknown
19:35.21blast007if we release on Github, it automatically generates a source tar/zip from the repo
19:35.59Constitutionah
19:36.46blast007and there's the "Download Zip" on the repo page
20:09.20*** join/#bzflag meeba (~lamer@c-73-14-146-7.hsd1.co.comcast.net)
20:27.18BulletCatcherThere should be only a couple of revisions with an even numbered release number (e.g., 2.4.2), so it isn't important to have a Git hash or anything else more specific for releases.
20:28.26BulletCatcherIt is only the odd numbered development versions where a Git hash would be informative.
20:31.06BulletCatcherWe ought to be able to arrange it to have the Git hash in the version string when building a development version from a Git tree, and fall back to the date otherwise, such as when a GitHub tar or zip file was used.
20:31.44blast007doh, good point..
22:29.57*** join/#bzflag BZnotify (~BZnotify@192.30.252.41)
22:29.57BZnotify[13bzflag] 15blast007 pushed 3 new commits to 062.4: 02http://git.io/vnWYG
22:29.57BZnotify13bzflag/062.4 14f8c3182 15Scott Wichser: Include .txt and .cfg files from plugins with the Windows installer.  Remove the bzfs configuration builder link and don't copy plugin templates, since there are no longer HTTP plugins that have any.
22:29.57BZnotify13bzflag/062.4 1416562be 15Scott Wichser: Copy .cfg files into the output directory so NSIS can easily find them for inclusion.
22:29.57BZnotify13bzflag/062.4 1462be574 15Scott Wichser: Rename help files to be in a consistent help_<pluginname>[_<topic>].txt format.
22:29.57*** part/#bzflag BZnotify (~BZnotify@192.30.252.41)
22:36.25*** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu)
23:15.57the_mapwait...
23:16.08blast007waits
23:16.11the_map<Constitution> aren't we being overly optimistic to think that there will actually be a 2.6 release at this point?
23:16.33the_mapare you all thinking about stopping bzflag development after the 2.4.4 release?
23:17.19blast007it's not planned, but dev activity isn't what it used to be, so he's simply questioning the likelyhood of a new major release
23:45.31BulletCatcherIt is easy to predict the future, but difficult to do so correctly.
23:47.22blast007yeah, where's my flying car?  :(
23:54.04BulletCatcherBe patient.
23:54.05BulletCatcherCurrent drone technology will eventually advance until drones can carry human passengers.
23:55.23BulletCatcherAdding an external speaker so it can sound like a Jetsons car will make it complete. :-)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.