[openssl-project] platforms

Richard Levitte levitte at openssl.org
Tue Jan 9 11:37:11 UTC 2018


In message <20180109.105624.1472224252969503988.levitte at openssl.org> on Tue, 09 Jan 2018 10:56:24 +0100 (CET), Richard Levitte <levitte at openssl.org> said:

levitte> In message <CAHEJ-S6JWVUFHMpjZQOguOqGRdQD792eyO68_n_Px90hM6KKRA at mail.gmail.com> on Tue, 9 Jan 2018 17:49:36 +1000, Tim Hudson <tjh at cryptsoft.com> said:
levitte> 
levitte> tjh> Given the discussion on PR#5035 it is time to split 10-main.conf into three groups to match the
levitte> tjh> platform policy and roadmap in my view.
levitte> tjh> 
levitte> tjh> 10-primary
levitte> tjh> 20-secondary
levitte> tjh> 30-community
levitte> tjh> 40-unknown
levitte> tjh> 50-deprecated
levitte> 
levitte> Arbitrary numbers will always be arbitrary.  We've already started
levitte> with new community contributed config targets in the 50 group, why
levitte> change that?

My proposal, which fits the numbering pattern we've started following
already, it this:

diff --git a/Configurations/README b/Configurations/README
index 9f31dfcd9e..f599610a8e 100644
--- a/Configurations/README
+++ b/Configurations/README
@@ -15,6 +15,30 @@ configuration in diverse ways:
                 information.
 
 
+Naming conventions for config files
+===================================
+
+Config files (*.conf) are named {nn}-{name}.conf, where {nn} is a two
+digit number and {name} is an indicator of what kind of configuration
+can be expected in the file.  The convention for {name} may be refined
+for some number groups.
+
+The number {nn} is somewhat loosely grouped as follows:
+
+00-09  Templates
+10-19  Primary platforms (*)
+20-49  Secondary platforms (*)
+50-69  Community provided platforms (*)
+70-88  Unknown platforms (*)
+89     Deprecated platforms (*)
+90-99  Personal configs (**)
+
+(*) See https://www.openssl.org/policies/platformpolicy.html
+(**) There may be some configs that team members use personally and
+     wish to share.  This also leaves space for those who want to
+     maintain their own configs inside their OpenSSL source checkout
+
+
 Configurations of OpenSSL target platforms
 ==========================================
 


I haven't made a PR from this yet, but am prepared to.

Cheers,
Richard

-- 
Richard Levitte         levitte at openssl.org
OpenSSL Project         http://www.openssl.org/~levitte/


More information about the openssl-project mailing list