unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: core-update scope
Date: Mon, 2 Sep 2024 13:37:12 -0400	[thread overview]
Message-ID: <ZtX3yAlw62jHDhu3@jasmine.lan> (raw)
In-Reply-To: <CAJsg1E8FtEzv0f723hf8EaZ4yX22z66VQyrr-1mR0kRaPUOafg@mail.gmail.com>

On Sat, Aug 31, 2024 at 02:32:01PM -0700, Andy Tai wrote:
> 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?

I don't think there is an obviously correct answer to this.

I have considered that Guix could have a "media team" that led the
effort for packages like FFmpeg and others that are in the middle layer
of the package graph and handle media. GStreamer is another candidate,
and of course all the codecs that FFmpeg and GStreamer depend on.

I think that "media" is generally expected by all users of desktop Guix,
and it's not uncommon to use headless Guix to play media (music players,
TV boxes, etc). So there should be lots of support :)

I'd be willing to help with this team if others were interested, but I
can't do it alone. I don't think it would be as hard as integrated
systems like GNOME or KDE, because the inter-package compatibility
requirements for media packages are usually lax, and so the media
formats are defined by standards and the respective codecs are treated
as black boxes by their users.


  reply	other threads:[~2024-09-02 17:37 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 [this message]
2024-09-04  9:01 ` Christopher Baines
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

  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=ZtX3yAlw62jHDhu3@jasmine.lan \
    --to=leo@famulari.name \
    --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 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).