[asterisk-bugs] [JIRA] Commented: (ASTERISK-20483) Allow Asterisk to report git SHAs in version string.

[Andrew Latham (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197675#comment-197675 ] 

Andrew Latham commented on ASTERISK-20483:
------------------------------------------

I agree with your concern.  I think we should push ahead a little bit and expect GIT on new platforms.  I can't think of a production machine today that would not have GIT as a means of version control or deployment scripts.

If you put the diff for the doxygen in https://issues.asterisk.org/jira/browse/ASTERISK-20259 and I will add it to my project.  I have over 1k lines to update soon...

> Allow Asterisk to report git SHAs in version string.
> ----------------------------------------------------
>
>                 Key: ASTERISK-20483
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20483
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Core/BuildSystem
>    Affects Versions: SVN
>            Reporter: Shaun Ruffell
>            Severity: Minor
>         Attachments: 0001-build_tools-Allow-Asterisk-to-report-git-SHAs-in-ver.patch
>
>
> From patch to be attached:
> {noformat}
> Make git more attractive for managing work-in-progress. Especially
> convenient when a potential patch set needs to be tested on multiple
> platforms since one can use git to keep all the test environments in
> sync independent of a subversion server.
> Now the Asterisk version will show the exact git SHA5 that was used
> when building (still appended by "M" if there are local
> modifications) from a git clone of the Asterisk repository so the
> developer can more easily know what is actually under test.
> You will now get this:
>   $ asterisk -V
>   Asterisk GIT-1698298
> Instead of this:
>   $ asterisk -V
>   Asterisk UNKNOWN__and_probably_unsupported
> This has zero impact for those not using git with the exception of
> an extra test in the configure script to gather the path of the git.
> This is necessary to prevent "sudo make install" from failing since
> git may not be in the path in make's shell environment.
> {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira