Add a counter field to RELEASE, just before the date, and fix it at zero. This allows custom package builds to override it in a way that sorts before the official packages. Example: Official release: 1.6.0-0.20160120.<githash> Custom release 1: 1.6.0-1.avi.20160121.<githash> Custom release 2: 1.6.0-2.avi.20160122.<githash> The counter (0/1/2) ensures that the build number dominates over the date when sorting. Message-Id: <20170122102814.19649-1-avi@scylladb.com>
25 lines
737 B
Bash
Executable File
25 lines
737 B
Bash
Executable File
#!/bin/sh
|
|
|
|
VERSION=666.development
|
|
|
|
if test -f version
|
|
then
|
|
SCYLLA_VERSION=$(cat version | awk -F'-' '{print $1}')
|
|
SCYLLA_RELEASE=$(cat version | awk -F'-' '{print $2}')
|
|
else
|
|
DATE=$(date +%Y%m%d)
|
|
GIT_COMMIT=$(git log --pretty=format:'%h' -n 1)
|
|
SCYLLA_VERSION=$VERSION
|
|
# For custom package builds, replace "0" with "counter.your_name",
|
|
# where counter starts at 1 and increments for successive versions.
|
|
# This ensures that the package manager will select your custom
|
|
# package over the standard release.
|
|
SCYLLA_BUILD=0
|
|
SCYLLA_RELEASE=$SCYLLA_BUILD.$DATE.$GIT_COMMIT
|
|
fi
|
|
|
|
echo "$SCYLLA_VERSION-$SCYLLA_RELEASE"
|
|
mkdir -p build
|
|
echo "$SCYLLA_VERSION" > build/SCYLLA-VERSION-FILE
|
|
echo "$SCYLLA_RELEASE" > build/SCYLLA-RELEASE-FILE
|