From e310677df7b3ce6506b35044abafcb507caa7e07 Mon Sep 17 00:00:00 2001
From: Rickard Green
The
A list of application versions that the application
depends on. An example of such an application version is
- "kernel-3.0". Application versions specified as runtime
+
Some dependencies might only be required in specific runtime + scenarios. In the case such optional dependencies exist, these are + specified and documented in the corresponding "App" documentation + of the specific application.
+The
All runtime dependencies specified in OTP applications + during the OTP 17 release might not be completely correct. This + is actively worked on. Declared runtime dependencies in OTP + applications are expected to be correct in OTP 18.
As of OTP release 17, the OTP release number corresponds to
- the major part of the OTP version. The OTP version as a concept was
- introduced in OTP 17. In the normal case, the OTP version will be
- constructed as
-
When a part in the version number is increased, all less significant
- parts are set to
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.
- -Application versions will be managed the same way as the OTP version.
- Application versions part of a release candidate will however not have an
-
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
If the version read from the
On a target system (see the
-
How to install Erlang/OTP on UNIX or Windows.
As of OTP release 17, the OTP release number corresponds to
+ the major part of the OTP version. The OTP version as a concept was
+ introduced in OTP 17. The
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.
+ +Release candidates have an
In an OTP source code tree, the OTP version can be read from
+ the text file
In an installed OTP development system, the OTP version can be read
+ from the text file
If the version read from the
No
The text file
+<OtpVersion> : <ChangedAppVersions> # <UnchangedAppVersions> ++
Using ordinary UNIX tools like
The above commands give a bit more information than the exact answers, + but adequate information when manually searching for answers to these + questions.
+The format of the
As of OTP 17.0 application versions will use the same
+
In the normal case, a version will be constructed as
+
When a part in the version number is increased, all less significant
+ parts are set to
An application version or an OTP version identifies source code + versions. That is, it does not imply anything about how the application + or OTP has been built.
+ +Version numbers in general are only partially ordered. However, + normal version numbers (with three parts) as of OTP 17.0 have a total + or linear order. This applies both to normal OTP versions and + normal application versions.
+ +When comparing two version numbers that have an order, one + compare each part as ordinary integers from the most + significant part towards less significant parts. The order is + defined by the first parts of the same significance that + differ. An OTP version with a larger version include all + changes that that are part of a smaller OTP version. The same + goes for application versions.
+ +In the general case, versions may have more than three parts. In
+ this case the versions are only partially ordered. Note that such
+ versions are only used in exceptional cases. When an extra
+ part (out of the normal three parts) is added to a version number,
+ a new branch of versions is made. The new branch has a linear
+ order against the base version. However, versions on different
+ branches have no order. Since they have no order, we
+ only know that they all include what is included in their
+ closest common ancestor. When branching multiple times from the
+ same base version,
An example of branched versions: The version
The following application versions were part of OTP 17.0. If + the normal part of an applications version number compares + as smaller than the corresponding application version in this list, + the version number does not adhere to the version scheme introduced + in OTP 17.0 and should be considered as not having an order against + versions used as of OTP 17.0.
+