On Tue, 2010-06-29 at 09:08 -0400, Chuck Rolke wrote: > I agree with Andrew for his stated reasons. After thinking about it a little > more how about this maybe a hybrid mix of #1 and #2 would work: > > 1. For each exe/dll, add a .rc file that puts some default version number and > an Apache Qpid icon. The icon is an elegant "Q" with the Apache feather for > the hook of the Q. > > 2. The post-build version patch would involve changing only the version text > string resource.
I might be missing something, but once you've got the rc files I can't see any point in a post processing step at all. You can centralise the version numbers in a single file that is included by all the rc files and this would be the only thing needing to change when the version numbers change. I think it is fairly important that the version numbers are actually checked in the source base somewhere so that you don't need some external knowledge to figure out the correspondence between the library versions and the source control versions. > > For folks who don't care about the version, they will get something that's > not unreasonable. For folks who do care about the version, the process of > patching the string resource is much easier. If you don't care about the version then this whole discussion is irrelevant! Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
