[mythtv-users] Build error.
Gavin Hurlbut
gjhurlbu at gmail.com
Fri Mar 11 03:10:27 UTC 2011
On Thu, Mar 10, 2011 at 6:19 PM, Michael Lynch <lynchmv at gmail.com> wrote:
> On Thu, Mar 10, 2011 at 5:49 PM, Jan Johansson <j2 at mupp.net> wrote:
> > I pulled a new git about an hour ago (how does one check revision with
> git
> > btw?)
> >
> >
>
> Here is how I get the version I pull from git. I clobbered together
> bits and pieces I found over the internet to come up with this:
>
> git describe |awk -F"." '{print $2}' |awk -F"-" '{print "0."$1"."$2}'
>
> It outputs something such as:
>
> lynchmv at slacke6400:~/src/mythtv$ git describe |awk -F"." '{print $2}'
> |awk -F"-" '{print "0."$1"."$2}'
> 0.25pre.1359
you use: git describe --dirty
That's all that's really needed. The version will be like:
v0.25pre-1397-gb584b68
the first part (to the -) corresponds to what the last tag was.. The second
is the number of commits after that tag, and the third (which IS necessary)
-- less the "g" -- is the beginning of the SHA1 of the last commit. There
can also be a -dirty at the end if you have custom stuff in there (not
committed).
I don't know why you'd want to decompose the git describe information in the
way the previous poster did. For support, the developers will be wanting
the version number as I outlined, and the branch you are on (from git
branch, it's the one with the * beside). This data is also compiled into
the binaries, and is available from "mythfrontend --version" or "mythbackend
--version".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20110310/ddb91f9e/attachment.html
More information about the mythtv-users
mailing list