Guix, Should we have a C++ team? I think project contributions regarding C and C++ compilers, libraries, tools, and programs would benefit from a tag to flag, discuss, and triage issues and a team branch to manage, test, and pre-build patches.
This team would of course be distinct from the core-packages team, which manages the most fundamental packages and challenging updates. Updates to C++ packages often result in a non-trivial number of dependent package builds, which makes patch review challenging and leads to overlooked or forgotten contributions and long-delayed merges. Also, widely used Guix C++ packages are several versions and many years out-of-date. A C++ team would help us to be more responsive both to contributors and upstream releases while maintaining a stable rolling-release and making efficient use of build farm compute and storage. Greg diff --git a/etc/teams.scm b/etc/teams.scm index fe3291f914..e257650a04 100755 --- a/etc/teams.scm +++ b/etc/teams.scm @@ -611,0 +612,14 @@ (define-team zig +(define-team c++ + (team 'c++ + #:name "C/C++ team" + #:description + "C and C++ compilers, libraries, tools, and programs" + #:scope (list "gnu/packages/c.scm" + "gnu/packages/cpp.scm" + "gnu/packages/llvm.scm" + "gnu/packages/llvm-meta.scm" + "gnu/packages/ninja.scm" + "gnu/packages/valgrind.scm" + "gnu/build/cmake-build-system.scm" + "gnu/build-system/cmake.scm"))) +
