From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Greg Hogan <code@greghogan.com>, guix-devel <guix-devel@gnu.org>
Subject: Re: Creating a C/C++ team?
Date: Sat, 30 Nov 2024 16:19:55 +0100 [thread overview]
Message-ID: <87v7w4ycis.fsf@gnu.org> (raw)
In-Reply-To: <dff5dd1983939f295f1c1fd481e2e7950f409ce5.camel@gmail.com> (Liliana Marie Prikler's message of "Fri, 29 Nov 2024 10:36:13 +0100")
Hi!
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> Am Montag, dem 25.11.2024 um 13:27 -0500 schrieb Greg Hogan:
[...]
>> 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 :)
Yes, the description could clarify that Greg wrote above, which is that
its scope is disjoint from that of the ‘core-packages’ team.
Ludo’.
next prev parent reply other threads:[~2024-11-30 15:20 UTC|newest]
Thread overview: 5+ 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
2024-11-30 15:19 ` Ludovic Courtès [this message]
2024-12-01 10:02 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7w4ycis.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=code@greghogan.com \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).