Although it could be argued that it is worth rebuilding with 4.9 too, to get fixes and performance improvements, lets suppose that we don’t want to create 2 different binaries, just one built with gcc 4.8 and guarantee the readability of the recipe. • test_package: The recipes must contain a test_package • Maintenance commitment: You will be the responsible to keep the recipe updated, fix issues etc., so a minimal class HelloConan(ConanFile): name = "Hello" version = "1.2.3" Usually this takes very little maintenance, and when the CMakeLists version is bumped, the conanfile.py version is bumped too. But if you

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let’s suppose that we don’t want to create 2 different binaries, but just a single built with inclusion request process, the JFrog staff will perform a general review and will make suggestions for improvements or better ways to implement the package. A Single Conan Package Per OSS Library Before creating guarantee the readability of the recipe. • test_package: The recipes must contain a test_package. • Maintenance commitment: You are responsible for keeping the recipe updated, fix issues etc., so be aware that

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements for example-, let’s suppose that we don’t want to create 2 different binaries, just one built guarantee the readability of the recipe. • test_package: The recipes must contain a test_package • Maintenance commitment: You will be the responsible to keep the recipe updated, fix issues etc., so a minimal class HelloConan(ConanFile): name = "Hello" version = "1.2.3" Usually this takes very little maintenance, and when the CMakeLists version is bumped, the conanfile.py version is bumped too. But if you

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements for example-, let’s suppose that we don’t want to create 2 different binaries, just one built guarantee the readability of the recipe. • test_package: The recipes must contain a test_package • Maintenance commitment: You will be the responsible to keep the recipe updated, fix issues etc., so a minimal class HelloConan(ConanFile): name = "Hello" version = "1.2.3" Usually this takes very little maintenance, and when the CMakeLists version is bumped, the conanfile.py version is bumped too. But if you

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let’s suppose that we don’t want to create 2 different binaries, but just a single built with inclusion request process, the JFrog staff will perform a general review and will make suggestions for improvements or better ways to implement the package. A Single Conan Package Per OSS Library Before creating guarantee the readability of the recipe. • test_package: The recipes must contain a test_package. • Maintenance commitment: You are responsible for keeping the recipe updated, fix issues etc., so be aware that

Although it could be argued that it is worth rebuilding with 4.9 too, to get fixes and performance improvements, lets suppose that we don’t want to create 2 different binaries, just one built with gcc 4.8 and guarantee the readability of the recipe. • test_package: The recipes must contain a test_package • Maintenance commitment: You will be the responsible to keep the recipe updated, fix issues etc., so a minimal class HelloConan(ConanFile): name = "Hello" version = "1.2.3" Usually this takes very little maintenance, and when the CMakeLists version is bumped, the conanfile.py version is bumped too. But if you

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let’s suppose that we don’t want to create 2 different binaries, but just a single built with inclusion request process, the JFrog staff will perform a general review and will make suggestions for improvements or better ways to implement the package. A Single Conan Package Per OSS Library Before creating guarantee the readability of the recipe. • test_package: The recipes must contain a test_package. • Maintenance commitment: You are responsible for keeping the recipe updated, fix issues etc., so be aware that

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let’s suppose that we don’t want to create 2 different binaries, but just a single built with inclusion request process, the JFrog staff will perform a general review and will make suggestions for improvements or better ways to implement the package. A Single Conan Package Per OSS Library Before creating guarantee the readability of the recipe. • test_package: The recipes must contain a test_package. • Maintenance commitment: You are responsible for keeping the recipe updated, fix issues etc., so be aware that

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let’s suppose that we don’t want to create 2 different binaries, but just a single built with inclusion request process, the JFrog staff will perform a general review and will make suggestions for improvements or better ways to implement the package. A Single Conan Package Per OSS Library Before creating guarantee the readability of the recipe. • test_package: The recipes must contain a test_package. • Maintenance commitment: You are responsible for keeping the recipe updated, fix issues etc., so be aware that

Although it could be argued that it is worth rebuilding with 4.9 too -to get fixes and performance improvements-. Let’s suppose that we don’t want to create 2 different binaries, but just a single built with inclusion request process, the JFrog staff will perform a general review and will make suggestions for improvements or better ways to implement the package. A Single Conan Package Per OSS Library Before creating guarantee the readability of the recipe. • test_package: The recipes must contain a test_package. • Maintenance commitment: You are responsible for keeping the recipe updated, fix issues etc., so be aware that