A Common Package Specification: Getting Build Tools to Talk to Each Other Lessons Learned From Making Thousands of Binaries Consumable by Any Build System Diego Rodriguez-Losada @ CppCon 2023Outline scripts Consuming a package 6 ZLib ? -I/include -L/lib -lzlibCommon Package Specification (CPS): Scope ZLib CPS 7 …Related work - CPS: https://cps-org.github.io/cps by Matthew Woehlke maintainers don’t want that - It is a “package” specification, not a “library” specification - But we can certainly separate, Common Library Specification (Libman) CPS “openssl” CLS “ssl” CLS “crypto”

Common Package Specification (CPS) in practice: A full round trip implementation in Conan C++ package manager CppCon24Outline - Introduction to Common Package Specification (CPS) - Creation of CPS libraries Build times Setting CI Managing CMake projects Why a Common Package Specification (CPS) 4Common Package Specification (CPS) ZLib zlib.cps 5 …Existing solutions Searching for Convergence in Standard C++ Dependency Management - Bret Brown and Bill Hoffman- CppCon2023 A Common Package Specification: Getting Build Tools to Talk to Each Other - Diego Rodriguez-Losada - CppCon2023 C++ Ecosystem

Security Configuration 1.1 Master Node Configuration Files 1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Scored) Result: Not Applicable Remediation: configuration is passed in as arguments at container run time. 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Scored) Result: Not Applicable Remediation: RKE doesn’t is passed in as arguments at container run time. 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Scored) Result: Not Applicable Remediation:

Security Configuration 1.1 Master Node Configuration Files 1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Scored) Result: Not Applicable Remediation: configuration is passed in as arguments at container run time. 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Scored) Result: Not Applicable Remediation: RKE doesn’t is passed in as arguments at container run time. 1.1.3 Ensure that the controller manager pod specification file permissions are set to 644 or more restrictive (Scored) Result: Not Applicable Remediation:

1.1.1 Ensure that the API server pod specification file permissions are set to 644 or more restrictive (Automated) 1.1.2 Ensure that the API server pod specification file ownership is set to root:root (Automated) that the controller manager pod specification file permissions are set to 644 or more restrictive (Automated) 1.1.4 Ensure that the controller manager pod specification file ownership is set to root:root 1.1.5 Ensure that the scheduler pod specification file permissions are set to 644 or more restrictive (Automated) 1.1.6 Ensure that the scheduler pod specification file ownership is set to root:root (Automated)

clear many interface related confusions. 5. Clarifies several ambiguities which exist in the Go specification, such as embedding rules, promoted method value evaluation, and panic/recover mechanism. 6. literals denoting values of basic types are called basic value literals. Boolean value literals Go specification doesn't define boolean literals. However, in general programming, we can view the two predeclared = π * 2, π * 0.5, "degree" 19. } Go specification calls each of the lines containing a = symbol in the above constant declaration group as a constant specification. In the above example, the * symbol

Export Declarations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 8.5 Specification of External Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 8.5.1 Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 11 Specification of Derived Instances 145 11.1 Derived instances of Eq and Ord . . . . . . . . . . . . . . . arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 14.6 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 15 Data

clear many interface related confusions. 5. Clarifies several ambiguities which exist in the Go specification, such as embedding rules, promoted method value evaluation, and panic/recover mechanism. 6. literals denoting values of basic types are called basic value literals. Boolean value literals Go specification doesn't define boolean literals. However, in general programming, we can view the two predeclared * 2, π * 0.5, "degree" 19 | } Go specification calls each of the lines containing a = symbol in the above constant declaration group as a constant specification. In the above example, the * symbol