[mythtv-users] Questions on version.sh (Gentoo ebuild)

[Tom Dexter]

On Mon, Mar 26, 2018 at 2:52 PM, Tom Dexter <digitalaudiorock at gmail.com> wrote:
> There's currently nobody actually maintaining any Gentoo ebuild for
> MythTV. I've been taking a stab at trying to get one working for
> fixes/29 based on the existing one for 0.28.1. I've run into a snag
> that someone here might be able to help with.
>
> The approach to the Gentoo ebuilds has generally been to download the
> source for a specific commit. In my case I'm using what appears to be
> the last commit for fixes/29, which is causing it to download the
> following:
>
> https://github.com/MythTV/mythtv/archive/067c37849fd536c8d98d73a281b5467946b043df.tar.gz
>
> The compile portion is failing on the version.sh script...which I can
> see changed a bit since 0.28...notably that it appears to have a check
> of the source version vs the binary version(?) that wasn't in there
> before. Also note that up until now, Gentoo has never required git for
> MythTV, so any "git" commands will fail..though that's always been the
> case. Specifically, I'm getting this:
>
> sh version.sh /var/tmp/portage/media-tv/mythtv-29.0/work/mythtv-29.0/mythtv
> cd libs; /usr/lib/qt5/bin/qmake QMAKE=/usr/lib/qt5/bin/qmake -o
> Makefile libs.pro
> version.sh: line 25: git: command not found
> version.sh: line 25: git: command not found
> Source Version created as v29.0-067c37849fd536c8d98d73a281b5467946b043df
> Info: creating stash file
> /var/tmp/portage/media-tv/mythtv-29.0/work/mythtv-29.0/mythtv/libs/.qmake.stash
> v29.0-067c37849fd536c8d98d73a281b5467946b043df
> cd filters; /usr/lib/qt5/bin/qmake QMAKE=/usr/lib/qt5/bin/qmake -o
> Makefile filters.pro
> ERROR: High level of source version
> v29.0-067c37849fd536c8d98d73a281b5467946b043df, does not match high
> level of binary version 30.20180319-1
>
> One thing that definitely looks wrong here is that the above ends up with this:
>
> grep BIN libs/libmythbase/mythversion.h
> #define MYTH_BINARY_VERSION "30.20180319-1"
>

Ahhh! Never mind. I screwed up in that that commit WAS in fact the
latest commit for master and not for fixes/29. Now I'm trying
60e40b352ab95a135ec2ab8f9f1ee93b4f9d245e and it seems to be going OK.

Sorry for the noise.

Tom