On Tuesday 29 November 2005 03:46 pm, Tom Lichti wrote: > Pascal Favre wrote: > > I made a proposition for the ivtv project, which was accepted by them. > > This is the original text: > > > > Hello > > > > I use a 0.4.1 branch. dmesg displays: "ivtv: version 0.4.1 > > (development svn snapshot revision 2839 ) loading" > > For me I do not want to see the latest trunk version (this revision > > changes always). I want to see the last commited version for this branch. > > With this revision number I can easily check if there were any changes > > made for my specific branch > > http://ivtvdriver.org/trac/browser/ivtv/branches/ (2834) > > > > I propose to use "svnversion -n -c ." (630:2834, the second value > > should be used) instead of "svnversion -n ." (2839) in the makefile. > > > > When helping people it is much easier, because the used revision can > > be quickly checked against the latest commited change for the branch. > > Help can be provided earlier, instead of the usual "do a svn update" > > first. > > > > Regards > > Ruud > > I like this idea, is there any harm in changing the following line in > mythcontext.h: > > #define MYTH_BINARY_VERSION "0.19.20051128-1" > > to something like > > #define MYTH_BINARY_VERSION "0.19.20051128-1 SVN Rev. 8089" > > or even better: > > #define MYTH_BINARY_VERSION "0.19.20051128-8089" > > Would it cause any problems elsewhere? After looking at the code, > app_binary_version is used as the variable, defined as a Qstring, so it > should work, no? > > I'll try it on my checkout and see what happens... :)
That would require recompiling everything (all plugins, etc) every time a user updated a checkout. Bad idea. Isaac _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
