[mythtv-users] Version Numbers, was: Program guide freezes ...

[Michael T. Dean]

On 04/19/2008 10:37 AM, Brian Wood wrote:
> On Apr 19, 2008, at 1:17 AM, Michael T. Dean wrote:
>>> (0.21.20080304-1)
>>>       
>> BTW, that's pretty much useless as far as version numbers go.  You
>> should post the complete output of mythfrontend --version.
>>
>> Stuart Morgan put a lot of time and effort into making that easily
>> available, so it would be /very/ nice if more people started using it.
>> (Mentioning here as I'm sure you'll help spread the word.  :)
>>     
> Thanks for that tip. My main purpose was to show I was using 0.21.  
> Especially at times like now, when folks are transitioning from 0.20  
> to 0.21, it's especially important to mention what you are running,  
> but of course it should be mentioned in just about any system-related  
> post.
>
> I see the output of --version is far more complete, I should have  
> thought of that.
>
> FWIW here's the output:
>
> MythTV Version   : exported
> MythTV Branch    : branches/release-0-21-fixes
> Library API      : 0.21.20080304-1
> Network Protocol : 40
> Options compiled in: ...

Is that an ATrpms package?  Just curious because, as you'll see below, 
other than the branch difference, yours looks a lot like mine from (an 
old) trunk (I've been gone for a month, so I didn't get to even switch 
to 0.21-fixes, yet):

$ mythfrontend --version
Please include all output in bug reports.
MythTV Version   : 16509M
MythTV Branch    : trunk
Library API      : 0.21.20080304-1
Network Protocol : 40
Options compiled in: ...

Notice the identical Library API version.  So, really, using the library 
API version doesn't even say whether you're using -fixes or trunk.

One of the main benefits of the --version output is its inclusion of the 
SVN revision number.  Unfortunately, most packagers tend to build in an 
exported directory (without SVN info), so the MythTV version is 
unavailable.  I'm pretty sure that Gentoo and Ubuntu packagers are 
running a script at build time that puts the SVN revision in so that 
it's available in the --version output even when built outside of the 
SVN working copy.

So, I'm just asking as it might be worth seeing if we can get the 
packager building your packages to use a similar script.

Thanks,
Mike