From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Creating a C/C++ team?
Date: Thu, 28 Nov 2024 09:26:47 +0100 [thread overview]
Message-ID: <87bjxz7ohk.fsf@gnu.org> (raw)
In-Reply-To: <CA+3U0Znsy6qD0pAPJXJBGqoUO0MRpucEtJpEMuNFhv6y5OeD1A@mail.gmail.com> (Greg Hogan's message of "Mon, 25 Nov 2024 13:27:43 -0500")
Hi Greg,
Greg Hogan <code@greghogan.com> skribis:
> 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.
That makes a lot of sense to me.
> 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.
All for it. I feel bad when you and others contribute tricky C++
package updates and they remain in the patch queue for weeks or months.
(Speaking of which, I hope you also get commit rights soon, which should
help boost this team’s work.)
Thanks for all the work so far and for the exciting perspective!
Ludo’.
next prev parent reply other threads:[~2024-11-28 8:27 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 [this message]
2024-11-29 9:36 ` Liliana Marie Prikler
2024-11-30 15:19 ` Ludovic Courtès
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=87bjxz7ohk.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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).