osrm-backend/scripts/update_dependencies.sh

#!/usr/bin/env bash

# Note: once the subtree merge from this script has been committed and pushed to
# a branch do not attempt to rebase the branch back onto master or the subdirectory
# structure will be lost.
# http://git.661346.n2.nabble.com/subtree-merges-lose-prefix-after-rebase-td7332850.html

OSMIUM_REPO=https://github.com/osmcode/libosmium.git
OSMIUM_TAG=v2.9.0

VARIANT_REPO=https://github.com/mapbox/variant.git
VARIANT_TAG=v1.1.0

VARIANT_LATEST=$(curl https://api.github.com/repos/mapbox/variant/releases/latest | jq ".tag_name")
OSMIUM_LATEST=$(curl https://api.github.com/repos/osmcode/libosmium/releases/latest | jq ".tag_name")

echo "Latest osmium release is $OSMIUM_LATEST, pulling in \"$OSMIUM_TAG\""
echo "Latest variant release is $VARIANT_LATEST, pulling in \"$VARIANT_TAG\""

read -p "Looks good? (Y/n) " ok

if [[ $ok =~ [yY] ]]
then
  git subtree pull -P third_party/libosmium/ $OSMIUM_REPO $OSMIUM_TAG --squash
  git subtree pull -P third_party/variant/ $VARIANT_REPO $VARIANT_TAG --squash
fi
Add script to update subtree-ed third party dependencies more easily. Note: this updates the subtrees immediately. Discussion: would it make sense to do something along the lines of: $ http --body https://api.github.com/repos/mapbox/variant/releases/latest \| jq ".tag_name" "v1.0" And warn the user if the latest release tag is not the tag the update script was called with. Or at least ask for confirmation? 2015-08-19 13:26:07 -04:00			`#!/usr/bin/env bash`

add note about dangers of post subtree merges rebases [skip ci] 2016-10-03 13:51:30 -04:00			`# Note: once the subtree merge from this script has been committed and pushed to`
			`# a branch do not attempt to rebase the branch back onto master or the subdirectory`
			`# structure will be lost.`
			`# http://git.661346.n2.nabble.com/subtree-merges-lose-prefix-after-rebase-td7332850.html`

Add script to update subtree-ed third party dependencies more easily. Note: this updates the subtrees immediately. Discussion: would it make sense to do something along the lines of: $ http --body https://api.github.com/repos/mapbox/variant/releases/latest \| jq ".tag_name" "v1.0" And warn the user if the latest release tag is not the tag the update script was called with. Or at least ask for confirmation? 2015-08-19 13:26:07 -04:00			`OSMIUM_REPO=https://github.com/osmcode/libosmium.git`
rename dep update file, bump to osmium@2.9.0 2016-10-03 13:08:45 -04:00			`OSMIUM_TAG=v2.9.0`
Add script to update subtree-ed third party dependencies more easily. Note: this updates the subtrees immediately. Discussion: would it make sense to do something along the lines of: $ http --body https://api.github.com/repos/mapbox/variant/releases/latest \| jq ".tag_name" "v1.0" And warn the user if the latest release tag is not the tag the update script was called with. Or at least ask for confirmation? 2015-08-19 13:26:07 -04:00
Integration scripts for Clang's Modernize and Tidy tool. New directory: `scripts/`, in which small scripts for developers reside. - `modernize`: runs all cpp files through `clang-modernize`, respecting out targeted compiler versions, applying C++11 transformations, doing syntax checks and formatting --- in parallel. - `tidy`: runs all cpp files through `clang-tidy`, with selected warnings only, since we do not want to warn on every small detail. Please check the talk slides for `clang-tidy` linked in the references! References: - http://clang.llvm.org/extra/clang-tidy/ - http://llvm.org/devmtg/2014-04/PDFs/Talks/clang-tidy%20LLVM%20Euro%202014.pdf - http://clang.llvm.org/extra/clang-tidy/checks/list.html - https://github.com/Project-OSRM/osrm-backend/pull/1603 2015-09-11 11:14:36 -04:00			`VARIANT_REPO=https://github.com/mapbox/variant.git`
mapbox/variant v1.0 -> v1.1 2016-03-24 16:26:31 -04:00			`VARIANT_TAG=v1.1.0`
Add script to update subtree-ed third party dependencies more easily. Note: this updates the subtrees immediately. Discussion: would it make sense to do something along the lines of: $ http --body https://api.github.com/repos/mapbox/variant/releases/latest \| jq ".tag_name" "v1.0" And warn the user if the latest release tag is not the tag the update script was called with. Or at least ask for confirmation? 2015-08-19 13:26:07 -04:00
Use curl instead of http in update script. 2015-08-28 06:40:40 -04:00			`VARIANT_LATEST=$(curl https://api.github.com/repos/mapbox/variant/releases/latest \| jq ".tag_name")`
			`OSMIUM_LATEST=$(curl https://api.github.com/repos/osmcode/libosmium/releases/latest \| jq ".tag_name")`
Add script to update subtree-ed third party dependencies more easily. Note: this updates the subtrees immediately. Discussion: would it make sense to do something along the lines of: $ http --body https://api.github.com/repos/mapbox/variant/releases/latest \| jq ".tag_name" "v1.0" And warn the user if the latest release tag is not the tag the update script was called with. Or at least ask for confirmation? 2015-08-19 13:26:07 -04:00
Check for releases and request user confirmation before updating subtrees 2015-08-19 14:20:43 -04:00			`echo "Latest osmium release is $OSMIUM_LATEST, pulling in \"$OSMIUM_TAG\""`
			`echo "Latest variant release is $VARIANT_LATEST, pulling in \"$VARIANT_TAG\""`

			`read -p "Looks good? (Y/n) " ok`

			`if [[ $ok =~ [yY] ]]`
			`then`
Actually do the subtree pull instead of just notifying the user 2015-08-19 14:22:57 -04:00			`git subtree pull -P third_party/libosmium/ $OSMIUM_REPO $OSMIUM_TAG --squash`
			`git subtree pull -P third_party/variant/ $VARIANT_REPO $VARIANT_TAG --squash`
Check for releases and request user confirmation before updating subtrees 2015-08-19 14:20:43 -04:00			`fi`