Tell the user to check out the latest tag rather than the branch.

When the InspIRCd 3.x branch forks this will tell the user to go
back to the latest tag on the branch.
This commit is contained in:
Peter Powell 2018-10-26 02:57:13 +01:00
parent 2d50984185
commit 0e397ff721
2 changed files with 3 additions and 2 deletions

View File

@ -20,7 +20,7 @@ If you encounter any bugs then [please file an issue](https://github.com/inspirc
## Installation
**The `master` branch contains the latest development version. If you are running a server then you probably want the `insp20` branch. You can obtain this from [the releases page](https://github.com/inspircd/inspircd/releases) or by running `git checkout insp20` if you are installing via Git.**
**The `master` branch contains the latest development version. If you are running a server then you probably want the `insp20` branch. You can obtain this from [the releases page](https://github.com/inspircd/inspircd/releases) or by running `git checkout $(git describe --abbrev=0 --tags insp20)` if you are installing via Git.**
Most InspIRCd users running a UNIX-like system build from source. A guide about how to do this is available on [the InspIRCd wiki](https://wiki.inspircd.org/Installation_From_Source).

3
configure vendored
View File

@ -244,7 +244,8 @@ affect the running of your server. It is recommended that you use a stable
version instead.
You can obtain the latest stable version from http://www.inspircd.org/ or by
running `git checkout insp20` if you are installing from Git.
running `<|GREEN git checkout $(git describe --abbrev=0 --tags insp20)|>` if you are
installing from Git.
EOW
if (!prompt_bool $interactive, 'I understand this warning and want to continue anyway.', $opt_development // 0) {
say STDERR 'If you understand this warning and still want to continue pass the --development flag.' unless $interactive;