all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, 43501@debbugs.gnu.org
Subject: bug#43501: gst-plugins-bad cannot be built on linux-armhf, breaking qemu
Date: Fri, 18 Sep 2020 23:40:13 -0400	[thread overview]
Message-ID: <87wo0q77t3.fsf@netris.org> (raw)
In-Reply-To: <878sd6zgii.fsf@gmail.com>

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> This occurs on master (commit 679d5e6b3dcac4ee1f419c04b3719fead0bd9ee5).
>
> qemu-minimal is not impacted, but the fully-fledged qemu package
> cannot be built, due to a dependency on gst-plugins-bad, which fails to
> build like:

It would be good to eliminate that dependency.  Ever since 'spice-gtk'
was added, it has included *every* gstreamer plugin package in its
'propagated-inputs'.  I'm not sure, but it may have been motivated by a
goal that some Guix developers have advocated, to make packages in Guix
work "out of the box" in a way that users of proprietary systems have
come to expect, i.e. with popular patented codecs included.

I think it's important that Guix core functionality should be usable
without installing a collection of patented media codecs.  Those plugins
should be purely optional.  In my opinion, we should find a way to
eliminate those dependencies.

       Mark




  reply	other threads:[~2020-09-19  3:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-19  1:45 bug#43501: gst-plugins-bad cannot be built on linux-armhf, breaking qemu Maxim Cournoyer
2020-09-19  3:40 ` Mark H Weaver [this message]
2020-09-19 14:24   ` bug#43501: Whitelisting/blacklisting transitive package dependencies Danny Milosavljevic
2020-09-20 22:00   ` bug#43501: gst-plugins-bad cannot be built on linux-armhf, breaking qemu Mark H Weaver
2020-09-22  2:36     ` Maxim Cournoyer
2020-09-24  4:41       ` bug#43501: gst-plugins-bad cannot be built on linux-armhf Maxim Cournoyer
2020-09-26 18:57         ` Mark H Weaver

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=87wo0q77t3.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=43501@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.