I as well agree, that the usage information should not be printed and that the warning does not make a lot of sense.
Anyway concerning your ideas in #2: Widelands is still in a alpha state - some of the features planned for a final release are not yet implemented, and quite a hand full of known bugs are left inside the game in each official build. So an output like "build-18-alpha" would be kind of unlogical - an alpha of alpha software.
Further the bzr version alone does not say that much about the development state, as Widelands is developed in trunk + different branches, so a bzr version from one of the branches can show a completely different development state, although it has the same version number than another version from trunk - that's why there is the [branchname] tag included.
And last but not least: A person running a development version must have thought about compiling Widelands him-/herself or downloading an inofficial build a some point. And if he/she just downloads it *somewhere* without checking the date or even the contense of the file... seriously that's nothing we can take care of ;)
Btw. (Release) means "no debug symbols" in difference to (Debug)
So please don't get me wrong - your bug is 100% valid. Thank you for posting! :)
I just want to say, that always taking care about a 100% understandable version number in every state of development is just over prowered for a game like Widelands, on which just 1-10 person a month are working on. ;)
I as well agree, that the usage information should not be printed and that the warning does not make a lot of sense.
Anyway concerning your ideas in #2: Widelands is still in a alpha state - some of the features planned for a final release are not yet implemented, and quite a hand full of known bugs are left inside the game in each official build. So an output like "build-18-alpha" would be kind of unlogical - an alpha of alpha software.
Further the bzr version alone does not say that much about the development state, as Widelands is developed in trunk + different branches, so a bzr version from one of the branches can show a completely different development state, although it has the same version number than another version from trunk - that's why there is the [branchname] tag included.
And last but not least: A person running a development version must have thought about compiling Widelands him-/herself or downloading an inofficial build a some point. And if he/she just downloads it *somewhere* without checking the date or even the contense of the file... seriously that's nothing we can take care of ;)
Btw. (Release) means "no debug symbols" in difference to (Debug)
So please don't get me wrong - your bug is 100% valid. Thank you for posting! :)
I just want to say, that always taking care about a 100% understandable version number in every state of development is just over prowered for a game like Widelands, on which just 1-10 person a month are working on. ;)