Commit 66581d24 authored by Pekka Paalanen's avatar Pekka Paalanen

README: refer to version numbers in meson.build

configure.ac is no more, and in meson.build there are no minor or patch
versions for libweston, only major.
Signed-off-by: Pekka Paalanen's avatarPekka Paalanen <pekka.paalanen@collabora.com>
parent be61a1ff
...@@ -165,14 +165,14 @@ The document provides the full details, with the gist summed below: ...@@ -165,14 +165,14 @@ The document provides the full details, with the gist summed below:
- Minor - new backward compatible features. - Minor - new backward compatible features.
- Patch - internal (implementation specific) fixes. - Patch - internal (implementation specific) fixes.
Weston and libweston have separate version numbers in configure.ac. All Weston and libweston have separate version numbers in meson.build. All
releases are made by the Weston version number. Libweston version number releases are made by the Weston version number. Libweston version number
matches the Weston version number in all releases except maybe pre-releases. matches the Weston version number in all releases except maybe pre-releases.
Pre-releases have the Weston micro version 91 or greater. Pre-releases have the Weston micro version 91 or greater.
A pre-release is allowed to install a libweston version greater than the Weston A pre-release is allowed to install a libweston version greater than the Weston
version in case libweston major was bumped. In that case, the libweston version version in case libweston major was bumped. In that case, the libweston version
must be Weston major + 1 and with minor and patch versions zero. must be Weston major + 1.
Pkg-config files are named after libweston major, but carry the Weston version Pkg-config files are named after libweston major, but carry the Weston version
number. This means that Weston pre-release 2.1.91 may install libweston-3.pc number. This means that Weston pre-release 2.1.91 may install libweston-3.pc
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment