[PATCH 3/4] added build command "release" to generate taged versions.

[Tim Niemeyer]

Hi

Am 28. Januar 2016 00:30:57 MEZ, schrieb Alexander Wunschik <freifunk at wunschik.net>:

Ich verstehe die Intention hinter dem Patch nicht. Hier wäre eine ausführliche commit message gut.

>Signed-off-by: Alexander Wunschik <freifunk at wunschik.net>
>---
> buildscript | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
>diff --git a/buildscript b/buildscript
>index 14107ee..a65fc97 100755
>--- a/buildscript
>+++ b/buildscript
>@@ -210,6 +210,13 @@ prebuild() {
> build() {
>     prebuild
> 
>+    #build command to create special release binaries
>+    case "$1" in
>+        "release")
>+            version=$(git describe --abbrev=0)

Das führt leider dazu, dass man nicht mehr erkennen kann, ob es ein release (git tag) ist oder ob bereits auf dem Tag neue commits liegen.

Tim

>+            ;;
>+    esac
>+
>     opath=$(pwd)
>     cd "$target"
>     cpus=$(grep -c processor /proc/cpuinfo)
>@@ -368,7 +375,7 @@ case "$1" in
>         echo "Normaly the build uses lower IO and System priorities, "
>   echo "you can append \"fast\" option, to use normal user priorities"
>             echo
>-            echo "Usage: $0 $1 [fast|debug]"
>+            echo "Usage: $0 $1 [release] [fast|debug]"
>             echo
>         else
>             build "$2"
>@@ -418,7 +425,7 @@ case "$1" in
>         echo "  selectbsp <bsp-file>"
>         echo "  prepare"
>         echo "  config openwrt"
>-        echo "  build [fast|debug]"
>+        echo "  build [release] [fast|debug]"
>         echo "  buildall <community-file> [fast]"
>         echo "  clean"
>         echo ""