Updated MapnikReleaseSteps (markdown)
parent
9e89feba71
commit
5e58286468
1 changed files with 4 additions and 1 deletions
|
@ -85,13 +85,16 @@ TARBALL_NAME="mapnik-v${MAPNIK_VERSION}"
|
||||||
git clone git@github.com:mapnik/mapnik.git ${TARBALL_NAME}
|
git clone git@github.com:mapnik/mapnik.git ${TARBALL_NAME}
|
||||||
cd ${TARBALL_NAME}
|
cd ${TARBALL_NAME}
|
||||||
git checkout "tags/v${MAPNIK_VERSION}"
|
git checkout "tags/v${MAPNIK_VERSION}"
|
||||||
|
git rev-list --max-count=1 HEAD > GIT_REVISION
|
||||||
cd ../
|
cd ../
|
||||||
rm -rf ${TARBALL_NAME}/.git
|
rm -rf ${TARBALL_NAME}/.git
|
||||||
rm -rf ${TARBALL_NAME}/.gitignore
|
rm -rf ${TARBALL_NAME}/.gitignore
|
||||||
tar cjf ${TARBALL_NAME}.tar.bz2 ${TARBALL_NAME}/
|
tar cjf ${TARBALL_NAME}.tar.bz2 ${TARBALL_NAME}/
|
||||||
```
|
```
|
||||||
|
|
||||||
Note: if creating a release candidate do instead:
|
Note: the GIT_REVISION file is used as per https://github.com/mapnik/mapnik/issues/1170. We write a file before making the tarball so that systems that do not have git installed or that download the raw tarball can still know the git revision and mapnik-config will report after source build.
|
||||||
|
|
||||||
|
If creating a release candidate do instead:
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
cd /tmp
|
cd /tmp
|
||||||
|
|
Loading…
Add table
Reference in a new issue