summaryrefslogtreecommitdiffstats
path: root/crypto/conf/keysets.pl
diff options
context:
space:
mode:
authorRichard Levitte <levitte@openssl.org>2019-11-05 17:28:50 +0100
committerRichard Levitte <levitte@openssl.org>2019-11-07 11:37:25 +0100
commit936c2b9e933eacae80d3489e5f7316589f3e9a07 (patch)
treebcc8e013817b791df5b290c5ec1892e93969b5fc /crypto/conf/keysets.pl
parentChange the logic and behaviour surrounding '--api' and 'no-deprecated' (diff)
downloadopenssl-936c2b9e933eacae80d3489e5f7316589f3e9a07.tar.xz
openssl-936c2b9e933eacae80d3489e5f7316589f3e9a07.zip
Update source files for deprecation at 3.0
Previous macros suggested that from 3.0, we're only allowed to deprecate things at a major version. However, there's no policy stating this, but there is for removal, saying that to remove something, it must have been deprecated for 5 years, and that removal can only happen at a major version. Meanwhile, the semantic versioning rule is that deprecation should trigger a MINOR version update, which is reflected in the macro names as of this change. Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/10364)
Diffstat (limited to 'crypto/conf/keysets.pl')
-rw-r--r--crypto/conf/keysets.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/crypto/conf/keysets.pl b/crypto/conf/keysets.pl
index 05b086f7fa..3c6eecd9ca 100644
--- a/crypto/conf/keysets.pl
+++ b/crypto/conf/keysets.pl
@@ -108,7 +108,7 @@ for ($i = 0; $i < 128; $i++) {
}
print "\n};\n\n";
-print "#if ! OPENSSL_API_3\n";
+print "#ifndef OPENSSL_NO_DEPRECATED_3_0\n";
print "static const unsigned short CONF_type_win32[128] = {";
for ($i = 0; $i < 128; $i++) {
print "\n " if ($i % 8) == 0;