unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Andy Tai <atai@atai.org>, 63208@debbugs.gnu.org
Subject: [bug#63208] [PATCH] gnu: gstreamer: Depend on glib-next
Date: Mon, 01 May 2023 19:27:35 +0200	[thread overview]
Message-ID: <1fd375c2cb1e62221bb91a5502f4bded3a72ffc7.camel@gmail.com> (raw)
In-Reply-To: <20230501161702.29513-1-atai@atai.org>

Am Montag, dem 01.05.2023 um 09:17 -0700 schrieb Andy Tai:
> * gnu/packages/gstreamer.scm: gstreamer: [arguments] (configure-
> flags): Add "--wrap-mode=nofallback" to ensure no subproject sources
> in repo are used
>   [propagated-inputs]: Use glib-next
>   [inputs]: Use glib-next
We prefer not to bundle things, tyvm.

> * gnu/packages/gstreamer.scm: gst-plugins-base:   [propagated-
> inputs]: Use glib-next
>   [inputs]: Use glib-next
> 
> * gnu/packages/gstreamer.scm: gst-plugins-bad:   [propagated-inputs]:
> Use glib-next. Add dav1d
>   [inputs]: Use glib-next
> 
> * gnu/packages/gstreamer.scm: gst-plugins-ugly:   [propagated-
> inputs]: Use glib-next
>   [inputs]: Use glib-next
> 
> * gnu/packages/gstreamer.scm: gst-editing-services   [propagated-
> inputs]: Use glib-next
>   [inputs]: Use glib-next
> ---
Is there a *good* reason to do this now?  Note that gnome-team is
working on getting glib 2.76 everywhere, including GStreamer.

Cheers




  reply	other threads:[~2023-05-01 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 16:17 [bug#63208] [PATCH] gnu: gstreamer: Depend on glib-next Andy Tai
2023-05-01 17:27 ` Liliana Marie Prikler [this message]
2023-05-01 18:50 ` [bug#63208] Andy Tai
2023-05-02  5:48 ` [bug#63208] [PATCH v2] gnu: gstreamer: Ensure no bundle sources used Andy Tai
2023-05-02 16:59   ` Liliana Marie Prikler

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=1fd375c2cb1e62221bb91a5502f4bded3a72ffc7.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=63208@debbugs.gnu.org \
    --cc=atai@atai.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).