From 3fd4e3e770fbed95fd6fa2d547945ac71256339c Mon Sep 17 00:00:00 2001 From: Rickard Green Date: Sun, 16 Feb 2014 00:54:08 +0100 Subject: Misc adjustments of OTP version --- system/doc/installation_guide/otp_version.xml | 71 +++++++++++++++++++++++++++ system/doc/installation_guide/part.xml | 1 + system/doc/installation_guide/xmlfiles.mk | 1 + 3 files changed, 73 insertions(+) create mode 100644 system/doc/installation_guide/otp_version.xml (limited to 'system/doc/installation_guide') diff --git a/system/doc/installation_guide/otp_version.xml b/system/doc/installation_guide/otp_version.xml new file mode 100644 index 0000000000..dcba2d1702 --- /dev/null +++ b/system/doc/installation_guide/otp_version.xml @@ -0,0 +1,71 @@ + + + + +
+ + 2014 + Ericsson AB. All Rights Reserved. + + + The contents of this file are subject to the Erlang Public License, + Version 1.1, (the "License"); you may not use this file except in + compliance with the License. You should have received a copy of the + Erlang Public License along with this software. If not, it can be + retrieved online at http://www.erlang.org/. + + Software distributed under the License is distributed on an "AS IS" + basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See + the License for the specific language governing rights and limitations + under the License. + + + + OTP version + + + + + + 2014-02-19 + + otp_version.xml +
+

As of OTP release 17, the OTP release number corresponds to + the major OTP version number. In the normal case, the OTP version + number will be constructed as + <Major>.<Minor>.<Patch>. However more + dot separated parts may exist. If all parts less significant than + Minor equals 0, they are omitted when printing the + version. Release candidates have an -rc<N> suffix. The + OTP version as a concept was introduced in OTP 17.

+

OTP of a specific version is a set of applications of + specific versions. The application versions identified by + an OTP version corresponds to application versions that + have been tested together by the Erlang/OTP team at Ericsson AB. + An OTP system can however be put together with applications from + different OTP versions. Such a combination of application versions + has not been tested by the Erlang/OTP team. It is therefore + always preferred to use OTP applications from one single OTP + version.

+

In an OTP source code tree as well as in an installed OTP + development system, the OTP version can be read from the text + file OTP_VERSION in the OTP installation root directory + (code:root_dir()).

+

If the version read from the OTP_VERSION file in a + development system has a ** suffix, the system has been + patched using the $ERL_TOP/otp_build patch_app tool. In + this case, the system consists of application versions from + multiple OTP versions. The version preceding the ** + suffix corresponds to the OTP version of the base system that + has been patched.

+

On a target system (see the + system principles + documentation) no OTP_VERSION file will exist. This since + one easily can create a target system where it is hard to even + determine the base OTP version.

+

Note that if a development system is updated by other means + than $ERL_TOP/otp_build patch_app, the OTP_VERSION + file may identify wrong OTP version.

+ + diff --git a/system/doc/installation_guide/part.xml b/system/doc/installation_guide/part.xml index 19808fd165..150df39512 100644 --- a/system/doc/installation_guide/part.xml +++ b/system/doc/installation_guide/part.xml @@ -31,6 +31,7 @@

How to install Erlang/OTP on UNIX or Windows.

 + diff --git a/system/doc/installation_guide/xmlfiles.mk b/system/doc/installation_guide/xmlfiles.mk index 3995c607af..245491ab94 100644 --- a/system/doc/installation_guide/xmlfiles.mk +++ b/system/doc/installation_guide/xmlfiles.mk @@ -17,6 +17,7 @@ # %CopyrightEnd% # INST_GUIDE_CHAPTER_FILES = \ + otp_version.xml \ install-binary.xml \ verification.xml \ INSTALL.xml \ -- cgit v1.2.3