[mythtv-users] mythtv version numbering

[David Hampton]

On Thu, 2025-02-06 at 16:22 -0500, James Abernathy wrote:
> I'm trying to sort out the mythtv version numbering.  
> 1, If you install from the Ubuntu ppa it is consistent based on when
> the build system created it.

> 2. If I build on Debian using mythtv-light packaging you get
> something like v35-Pre-783-g5762763d2a

Let's see if I remember this properly.  v35 pre-release, 783 commits
since the v35-Pre tag was created, build at commit hash 5762763d2a. 
This is what you would expect from a source build.

> 3. If I build on Debian using the cmake process you get a similar
> number, v35-Pre-783-g5762763d2a

Same

> 4. When I build following the wiki
> (https://www.mythtv.org/wiki/Installing_MythTV_on_Debian) I get a
> version that is based on the date 35.0~master.20250205.4c4ec5e0-
> 0ubuntu0_amd64.deb and I can't relate that to anything.

Version 35.0 (not true, its a pre-release), master branch, build date
20250205, git commit 4c4ec5e0, followed by ubuntu stuff.

> The weird thing I can't figure out is, today, I took a backend that
> was built using the Debian 12 wiki method and removed that packaged
> and built using the cmake method.  It worked but now instead of the
> v35-Pre-784 type version I'm seeing v35.0~master.20250205.4c4ec5e0-
> 0ubuntu0.

That's odd.  Maybe you need to fetch tags?  Try "git fetch -t".

> So my question is how is the version numbering setup?  I like the
> v35-Pre-784 type because I can relate it to other versions on other
> systems.  But something is remaining after I removed the .deb package
> that is messing with the cmake numbering.

No idea why the deb packaging numbers things like that.  The name is
typically built from what data can be found from git and from the
filesystem.  You can look at mythtv/version.sh or the
mythtv_find_source_version function in cmake/SourceVersion.cmake to see
how the sausage is made.

David