forked from openpmix/openpmix
-
Notifications
You must be signed in to change notification settings - Fork 0
/
VERSION
128 lines (107 loc) · 4.81 KB
/
VERSION
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
# Copyright (c) 2008 Sun Microsystems, Inc. All rights reserved.
# Copyright (c) 2008-2011 Cisco Systems, Inc. All rights reserved.
# Copyright (c) 2011 NVIDIA Corporation. All rights reserved.
# Copyright (c) 2013 Mellanox Technologies, Inc.
# All rights reserved.
# Copyright (c) 2014-2016 Intel, Inc. All rights reserved.
# Copyright (c) 2022 IBM Corporation. All rights reserved.
# This is the VERSION file for PMIx, describing the precise
# version of PMIx in this distribution. The various components of
# the version number below are combined to form a single version
# number string.
# major, minor, and release are generally combined in the form
# <major>.<minor>.<release>.
major=6
minor=0
release=0
# greek is used for alpha or beta release tags. If it is non-empty,
# it will be appended to the version number. It does not have to be
# numeric. Common examples include a1 (alpha release 1), b1 or (beta release 1).
# The only requirement is that it must be entirely printable ASCII
# characters and have no white space.
greek=a1
# PMIx required dependency versions.
# List in x.y.z format.
hwloc_min_version=2.1.0
event_min_version=2.0.21
automake_min_version=1.13.4
autoconf_min_version=2.69.0
libtool_min_version=2.4.2
flex_min_version=2.5.4
# PMIx Standard Compliance Level
# The major and minor numbers indicate the version
# of the official PMIx Standard that is supported
# by this release. The extension number tracks how
# far beyond that Standard this implementation has
# gone. It is incremented whenever a release ADDS
# something beyond the Standard. An extension of "1"
# therefore indicates that something beyond the
# indicated Standard level has been added. A
# subsequent release that did not further add
# attributes or APIs to the implementation would
# retain the same extension value - if it did
# include further extensions, then the extension
# value would increment to "2" regardless of the
# magnitude of the changes.
std_major=4
std_minor=1
std_extension=2
# PMIx Standard ABI Compliance Level(s)
# The major and minor numbers (MAJOR.MINOR) indicate the version
# of the official PMIx Standard ABI that is supported
# by this release. This may be a comma separated list (no spaces)
# if more than one PMIx Standard ABI level is supported.
# The PMIx Standard defines a 'stable' and a 'provisional' ABI.
# Therefore, there are two sets of major/minor values.
# Since no PMIx Standard ABI exists at the moment, set to "0.0"
std_abi_stable=0.0
std_abi_provisional=0.0
# If repo_rev is empty, then the repository version number will be
# obtained during "make dist" via the "git describe --tags --always"
# command, or with the date (if "git describe" fails) in the form of
# "date<date>".
repo_rev=
# If tarball_version is not empty, it is used as the version string in
# the tarball filename, regardless of all other versions listed in
# this file. For example, if tarball_version is empty, the tarball
# filename will be of the form
# openmpi-<major>.<minor>.<release><greek>.tar.*. However, if
# tarball_version is not empty, the tarball filename will be of the
# form openmpi-<tarball_version>.tar.*.
tarball_version=
# The date when this release was created
date="Unreleased developer copy"
# The shared library version of each of PMIx's public libraries.
# These versions are maintained in accordance with the "Library
# Interface Versions" chapter from the GNU Libtool documentation:
#
# - If the library source code has changed at all since the last
# update, then increment revision (`c:r:a' becomes `c:r+1:a').
#
# - If any interfaces have been added, removed, or changed since
# the last update, increment current, and set revision to 0.
#
# - If any interfaces have been added since the last public release,
# then increment age.
#
# - If any interfaces have been removed since the last public release,
# then set age to 0.
#
# All changes in these version numbers are dictated by the PMIx
# release managers (not individual developers). Notes:
# 1. Since the PMIx master branch is maintained to always be compatible
# with all prior releases (i.e., we never remove an interface), the
# libtool 'c', 'r', and 'a' values are maintained equal to the highest
# values found on any given release branch. This ensure that the .so
# value remains the same as on the release branches, thereby indicating
# compatibility.
# 2. The version number of libpmix refers to the public pmix interfaces.
# It does not refer to any internal interfaces.
# Version numbers are described in the Libtool current:revision:age
# format.
libpmix_so_version=20:0:18
# "Common" components install standalone libraries that are run-time
# # linked by one or more components. So they need to be versioned as
# # well. Yuck; this somewhat breaks the
# # components-don't-affect-the-build-system abstraction.
#