The default remains the same: we show the huge ClueCon nag banner on
startup and in fs_cli.
However, if you pass --disable-huge-cluecon-nag, no banner will be
shown.
If you pass --enable-modest-cluecon-nag, a modest text-based ClueCon
reminder will be shown instead.
Our main version string is designed for release engineering purposes:
it matches file name conventions used for versioned tarballs and the
versions sort lexicographically while containing all pertinent
information.
With this commit we add in parentheses a more human-friendly rendering
of the version string: we spell out the meaning of each field and
render the datetime in RFC 822 notation.
sed: 1: "/#define *SWITCH_VERSIO ...": bad flag in substitute command: '}'
Reported-by: scruz in #freeswitch @ irc.freenode.net
Signed-off-by: Stefan Knoblich <s.knoblich@axsentis.de>
This amends commit f8be71ac6d.
This still should resolve FS-4303.
What's going on here is that we need a portable way to access
strftime. date(1posix) doesn't provide enough. And without perl, I
can't think of a better way to get to it than just using C. So the
logic for generating the extended revision has been moved into a small
self-contained and hopefully portable C program.
The revision was no longer picking up the last git commit. Instead,
it was showing the last release. This commit appends the last git
commit hash to the last release if a git repository is available.
Further, it checks whether there are uncommitted changes in the git
repository and adds an unclean tag to the version if this is the case.
Note that currently this will append the git commit hash even on a
tagged release if built directly from a git repository. Perhaps this
isn't such a bad thing, but if it turns out not to be desired, I have
an idea on how to squelch this without making unwarranted assumptions
about the remote layout of someone's local repository.
Michael Jerris