From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id COFUMDctS2cDJwEAqHPOHw:P1 (envelope-from ) for ; Sat, 30 Nov 2024 15:20:23 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id COFUMDctS2cDJwEAqHPOHw (envelope-from ) for ; Sat, 30 Nov 2024 16:20:23 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=YWSK++bR; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org" Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 214B964A11 for ; Sat, 30 Nov 2024 16:20:23 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tHPGL-0000YJ-MK; Sat, 30 Nov 2024 10:20:01 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tHPGK-0000Y9-4l for guix-devel@gnu.org; Sat, 30 Nov 2024 10:20:00 -0500 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tHPGJ-0004c3-MZ; Sat, 30 Nov 2024 10:19:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=684cspgeAr2wW8rkL9yzS5quaPOXYJ6tu9zFkPZbUqw=; b=YWSK++bRjE/MZJ6mZkJv VBvljOmebYyLMxiV482+mG5k/Ew1FUdmshlVu8iAo4t+d31my6HOwZYiVHRLoQ6xlK8nvql96faQK IKuANwbU3qOEWENHWjZa93gcuemuh6QI3U3tHez/iijg3Rn22wjzYp4D35CqBKP1vpHVitrj8P5Dm H+veYhgiXDEshrAn1L9o1w1Ovy48VnkkC8ywoVDoOabUjQy6iiwyd17YUsxght5pGT7X1FRWRkmXg MZ2Q9YCYAG6QpPULI8sGb1dPffREJ2tZhUTUj+xvU7z8PNWjPsmREoSMkWuMRZqqRMAbtW0hP7I5m Q79tDeo71IWD4Q==; From: =?utf-8?Q?Ludovic_Court=C3=A8s?= To: Liliana Marie Prikler Cc: Greg Hogan , guix-devel Subject: Re: Creating a C/C++ team? In-Reply-To: (Liliana Marie Prikler's message of "Fri, 29 Nov 2024 10:36:13 +0100") References: X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: =?utf-8?Q?D=C3=A9cadi?= 10 Frimaire an 233 de la =?utf-8?Q?R=C3=A9volution=2C?= jour de la Pioche X-PGP-Key-ID: 0x090B11993D9AEBB5 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 3CE4 6455 8A84 FDC6 9DB4 0CFB 090B 1199 3D9A EBB5 X-OS: x86_64-pc-linux-gnu Date: Sat, 30 Nov 2024 16:19:55 +0100 Message-ID: <87v7w4ycis.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -4.20 X-Spam-Score: -4.20 X-Migadu-Queue-Id: 214B964A11 X-Migadu-Scanner: mx12.migadu.com X-TUID: RJy7ib5zm+Nr Hi! Liliana Marie Prikler 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++ >> +=C2=A0 (team 'c++ >> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 #:name "C/C++ team" >> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 #:description >> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "C and C++ compilers, librar= ies, 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 =E2=80=98core-packages=E2=80=99 team. Ludo=E2=80=99.