all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Greg Hogan <code@greghogan.com>, guix-devel <guix-devel@gnu.org>
Subject: Re: Creating a C/C++ team?
Date: Fri, 29 Nov 2024 10:36:13 +0100	[thread overview]
Message-ID: <dff5dd1983939f295f1c1fd481e2e7950f409ce5.camel@gmail.com> (raw)
In-Reply-To: <CA+3U0Znsy6qD0pAPJXJBGqoUO0MRpucEtJpEMuNFhv6y5OeD1A@mail.gmail.com>

Hi Greg,

Am Montag, dem 25.11.2024 um 13:27 -0500 schrieb Greg Hogan:
> 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.
I think there is a risk that this still overlaps with core-packages on
the account of GCC being our main C/C++ toolchain.

Note: while I'm already swamped with work on gnome and emacs, I would
be interested in joining a hypothetical c++ team.

> 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"
I would limit the scope to "libraries and tools".  That programs happen
to be written in C/C++ is almost always incidental :)

> +        #:scope (list "gnu/packages/c.scm"
> +                      "gnu/packages/cpp.scm"
Of course.

> +                      "gnu/packages/llvm.scm"
> +                      "gnu/packages/llvm-meta.scm"
Not sure about these two.  Since our main use for LLVM is in
Rust/Zig/Mesa, all of which have their own teams, maybe we should leave
a broader LLVM team with members from all of that open for folks who
are not necessarily interested in the rest of C/C++.

> +                      "gnu/packages/ninja.scm"
> +                      "gnu/packages/valgrind.scm"
If we add these, I would also suggest adding build-tools.scm,
check.scm, debug.scm etc.

> +                      "gnu/build/cmake-build-system.scm"
> +                      "gnu/build-system/cmake.scm")))
These are under guix/ and belong to the core team IIRC.

Cheers


      parent reply	other threads:[~2024-11-29  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 18:27 Creating a C/C++ team? Greg Hogan
2024-11-28  8:26 ` Ludovic Courtès
2024-11-29  9:36 ` Liliana Marie Prikler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dff5dd1983939f295f1c1fd481e2e7950f409ce5.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=code@greghogan.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.