[quoted lines by Nicolas Pitre on 2007/04/30 at 14:52 -0400] >Ah, hmm, no. I didn't mean the existing driver version string at all. I >really mean to have a separate symbol automatically added to each >dynamically loaded driver pointing to that string with the global BRLTTY >version.
Yes, I understand now. >And that string may not only be "BRLTTY version 3.8" but it >should also include the svn revision number as reported by svn during >the build process, like $(svn info | sed -ne 's/^Revision: //p') as well >to be safe. It would need to be autogenerated and included in the .tgz >distribution of course. Yes. It'd be nice for this to work when the source tree has been exported (rather than checked out) as well. This is something I haven't figured out how to do yet. Does anyone know how to get svn export to produce a reliable revision number? For checked out source I'd use the svnversion command, but, of course, that doesn't work for exported source. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. http://FamilyRadio.com/ | http://Mielke.cc/bible/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty