Use markit solution for source code

[BradleyA]

# >>>   In the future, Use markit solution for source code and create a wrapper during compile/build time ?
# >>>       This will change the extension case statement objective: move from comments to variables in compiled code
# >>>       move from comments in source code to variables in compiled code
# >>>       very different vision
# >>>     Use markit in the source code & insert; var BUILD_VERSION="${FILE_RELEASE}.`git rev-list HEAD | wc -l`"
# >>>      Or use markit; to create CHAR variable found in compiled code ?
# >>>           opening comment x.c 'var VERSION="' and ending comment '"'
# >>>           opening comment x.c 'char VERSION[] = "$Version: ' ${FILE_NAME}    ${FILE_RELEASE}.`git rev-list HEAD | wc -l`     ${TIME_STAMP} ${USER} `hostname -f` `git describe` and ending comment '$";'
# >>>                           x.o $Version: XXXX XXXX XXXX XXXX '$'
# >>>           opening comment x.c 'char VERSION_MESSAGE[] = "$Version_message: ' ${FILE_MESSAGE} ` and ending comment '$";'
# >>>                           x.o $Version_message: XXXX '$'

[BradleyA]

This is going to require line1 and line 2 ${BEGIN_COMMENT_CHAR}

[BradleyA]

https://github.com/dustin/memcached/commit/923a335bf8613696d658448cd9c48a963924d436

Use git's version number for releases.

This will allow more specific version numbers, while simplifying a
proper release down to a tag and make dist.

During development, ./version.sh needs to run periodically to update
the version number. I'd recommend just adding a call to version.sh as
a git post commit hook:

% cat .git/hooks/post-commit

echo "Updating version."
./version.sh

(and make sure the file is executable)

.gitignore

/version.m4

version.sh

#!/bin/sh

if git describe > version.tmp
then
    echo "m4_define([VERSION_NUMBER], [`tr -d '\n' < version.tmp`])" \
        > version.m4
fi
rm version.tmp