unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	Tobias Geerinckx-Rice <me@tobias.gr>,
	Marius Bakke <marius@gnu.org>,
	67880@debbugs.gnu.org, Christopher Baines <guix@cbaines.net>,
	Janneke Nieuwenhuizen <janneke@gnu.org>
Subject: [bug#67880] [PATCH] teams: Add ‘core-packages’ team.
Date: Fri, 05 Jan 2024 12:04:57 +0100	[thread overview]
Message-ID: <87edewf3c6.fsf@gnu.org> (raw)
In-Reply-To: <87mstyi67c.fsf@gnu.org> (Mathieu Othacehe's message of "Mon, 25 Dec 2023 17:43:03 +0100")

Hi!

Mathieu Othacehe <othacehe@gnu.org> skribis:

>> +(define-team core-packages
>> +  (team 'core-packages
>> +        #:name "Core packages"
>> +        #:description "Core packages: the GNU tool chain, Guile, Coreutils, etc."
>> +        #:scope (list "gnu/packages/base.scm"
>> +                      "gnu/packages/bootstrap.scm"
>> +                      "gnu/packages/commencement.scm"
>> +                      "gnu/packages/cross-base.scm"
>> +                      "gnu/packages/gcc.scm"
>> +                      "gnu/packages/guile.scm"
>> +                      "gnu/packages/make-bootstrap.scm"
>> +                      "guix/build/gnu-build-system.scm"
>> +                      "guix/build/utils.scm"
>> +                      "guix/build-system/gnu.scm")))
>
> Seems nice.

Cool, I’m applying the patch.

> This has probably already been discussed, but should core-updates be
> renamed core-packages here to be more inline with the teams workflow?

IMO yes, that’s the logical next step.  (Maybe we can wait until the
next cycle though, dunno.)

Thanks,
Ludo’.




      reply	other threads:[~2024-01-05 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 18:01 [bug#67880] [PATCH] teams: Add ‘core-packages’ team Ludovic Courtès
2023-12-25 16:43 ` Mathieu Othacehe
2024-01-05 11:04   ` Ludovic Courtès [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

  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=87edewf3c6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=67880@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=guix@cbaines.net \
    --cc=janneke@gnu.org \
    --cc=marius@gnu.org \
    --cc=me@tobias.gr \
    --cc=othacehe@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).