https://github.com/tueda/test-versioning
An example for maintaining software versions by tags in the git repository.
https://github.com/tueda/test-versioning
Last synced: about 2 months ago
JSON representation
An example for maintaining software versions by tags in the git repository.
- Host: GitHub
- URL: https://github.com/tueda/test-versioning
- Owner: tueda
- Created: 2016-05-11T20:25:49.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2016-05-19T19:33:07.000Z (about 10 years ago)
- Last Synced: 2025-03-22T13:43:02.975Z (about 1 year ago)
- Language: Shell
- Homepage:
- Size: 7.81 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# test-versioning
An example for maintaining software versions by tags in the git repository.
The version number is fetched from tags like `v1.0.0`. The standard build
procedure works as
```
autoreconf -i
./configure
make
```
Changes in the repository are checked by `make` every time, and the sample
executable is rebuilt when needed.
Tarballs generated by `make dist` store the version when they are generated from
the repository. Then
```
./configure
make
```
should work. In this case, the version number is frozen and never changed.
## Caveat
The version number for `AC_INIT` is not automatically updated. You need to
occasionally run `autoreconf -f`, e.g., before `make dist`.