all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: core-update scope
Date: Wed, 04 Sep 2024 10:01:28 +0100	[thread overview]
Message-ID: <87cyljhjx3.fsf@cbaines.net> (raw)
In-Reply-To: <CAJsg1E8FtEzv0f723hf8EaZ4yX22z66VQyrr-1mR0kRaPUOafg@mail.gmail.com> (Andy Tai's message of "Sat, 31 Aug 2024 14:32:01 -0700")

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

Andy Tai <atai@atai.org> writes:

> Hi, shall changes to non-core packages like ffmpeg still be in the
> scope of core-updates?
>
> ffmpeg, for example, is no where near the core of the GNU system like
> glibc, but still it is widely dependent upon.   But it would make no
> sense to have a ffmpeg-team because it is used by packages over wide
> areas, KDE, GNOME and others.   It is not well defined in a package
> realm like GNOME packages.
>
> The last core-update branch was used to update ffmpeg.  This seems to
> still better to be true or to remain the same, no?

It doesn't seem like a core package to me, but also every branch doesn't
need a team. It's fine to have a ffmpeg or ffmpeg-update branch and just
bump that one package.

There's a balance to be struck in grouping packages together to both
minimise builds but also make changes easier to test.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  parent reply	other threads:[~2024-09-04  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 21:32 core-update scope Andy Tai
2024-09-02 17:37 ` Leo Famulari
2024-09-04  9:01 ` Christopher Baines [this message]
2024-09-07 17:47   ` Leo Famulari
2024-09-08 13:31     ` Andreas Enge

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=87cyljhjx3.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=atai@atai.org \
    --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.