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 projects Why a Common Package Specification (CPS) 4Common Package Specification (CPS) ZLib zlib.cps 5 …Existing solutions Searching for Convergence in C++ Package Management - Bret Brown & Daniel Daniel Ruoso - CppNow 2022 Case For a Standardized Package Description Format for External C++ Libraries by Luis Caro Campos - CppCon22 6 set(_ZLIB_x86 "(x86)") set(_ZLIB_SEARCH_NORMAL PATHS "[HKEY_LOC

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 configuration: Windows, x86_64, VS-2022, Release, static library 3. Install (system package manager or language package manager), build from source by the user, with that configuration 4. Pass information main(void){ … deflateInit(&defstream, Z_BEST_COMPRESSION); Build system scripts What is a package 5 ZLib - Independent unit of build and release (versionable) - Ready to use (binary)#include

1October 3, 2023 2 Libraries: A First Step Toward Standard C++ Dependency Management Bret Brown, C++ Infrastructure Lead, Bloomberg Bill Hoffman, CTO, KitwareHello! Welcome! Bret Brown C++ Infrastructure https://gitlab.kitware.com/bill-hoffman 3Goals 4Non-goals (so far) ● Package archive formats ○ .deb, .rpm, .pkg.tar.zst, NUPKG ● Package managers ○ APT, RPM, PKGBUILD, WPM ● Source repository structure workflows ○ ./configure && make && make install Why not? Scope and adoption friction! 5Then what? ● Package archive contents ○ i.e., dpkg-deb --contents fangorn.deb ● Metadata file(s) to declare those contents

Ov Over erview view Casdoor is a UI-first Identity Access Management (IAM) / Single-Sign-On (SSO) platform based on OAuth 2.0, OIDC, SAML, and CAS. Casdoor serves both the web UI and the login requests separate architecture, developed by Golang. It supports high concurrency, provides a web-based UI for management, and supports localization in 10+ languages. 2. Casdoor supports third-party application login and it supports extending third-party login with plugins. 3. Casdoor supports authorization management based on Casbin. It supports ACL, RBAC, ABAC, and RESTful access control models. 4. Casdoor provides

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.1.1. Dependency Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.2.1. Using the “default” Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 4.25. Monitoring and Management over JMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

........................................................................... 165 8.3.1. Context management and caching ....................................................................... 166 8.3.2. fixtures .................................................................. 166 8.3.3. Transaction management .................................................................................... 168 8.3.4 ........................................................................... 172 9. Transaction management ..............................................................................................

........................................................................... 166 8.3.1. Context management and caching ....................................................................... 167 8.3.2. fixtures .................................................................. 167 8.3.3. Transaction management .................................................................................... 169 8.3.4 ........................................................................... 173 9. Transaction management ..............................................................................................

........................................................................... 165 8.3.1. Context management and caching ....................................................................... 166 8.3.2. fixtures .................................................................. 166 8.3.3. Transaction management .................................................................................... 168 8.3.4 ........................................................................... 172 9. Transaction management ..............................................................................................

........................................................................... 167 8.3.1. Context management and caching ....................................................................... 168 8.3.2. fixtures .................................................................. 168 8.3.3. Transaction management .................................................................................... 170 8.3.4 ........................................................................... 174 9. Transaction management ..............................................................................................