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: Sun, 20 Sep 2020 18:00:29 -0400 [thread overview]
Message-ID: <87zh5kw1k7.fsf@netris.org> (raw)
In-Reply-To: <87wo0q77t3.fsf@netris.org>
Earlier, I wrote:
> Ever since 'spice-gtk' was added, it has included *every* gstreamer
> plugin package in its 'propagated-inputs'.
On my private branch, I removed 'gst-libav', 'gst-plugins-bad' and
'gst-plugins-ugly' from the propagated-inputs of 'spice-gtk'.
--8<---------------cut here---------------start------------->8---
diff --git a/gnu/packages/spice.scm b/gnu/packages/spice.scm
index 4aff8dbf56..4b4c673a9d 100644
--- a/gnu/packages/spice.scm
+++ b/gnu/packages/spice.scm
@@ -144,11 +144,8 @@ which allows users to view a desktop computing environment.")
(build-system gnu-build-system)
(propagated-inputs
`(("gstreamer" ,gstreamer)
- ("gst-libav" ,gst-libav)
("gst-plugins-base" ,gst-plugins-base)
("gst-plugins-good" ,gst-plugins-good)
- ("gst-plugins-bad" ,gst-plugins-bad)
- ("gst-plugins-ugly" ,gst-plugins-ugly)
("spice-protocol" ,spice-protocol)
;; These are required by the pkg-config files.
--8<---------------cut here---------------end--------------->8---
I rebuilt my system and user profiles with this patch applied, and
everything seems to work fine. Moreover, I'm glad to report that
'gst-plugins-ugly' is no longer in my store. (Sadly, 'gst-plugins-bad'
still is, because our 'gnome' package depends on 'cheese' which depends
on 'gst-plugins-bad', and last I checked that was unavoidable.)
I haven't tried using the 'spice' functionality specifically, but I
suspect that any reduced "out-of-the-box" functionality could be
regained by users simply installing those plugins as needed, along with
gstreamer for its 'native-search-paths' field.
What do you think?
Mark
PS: Danny's idea is worth considering in its own right, but I think it's
orthogonal to this proposed change.
next prev parent reply other threads:[~2020-09-20 22:02 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
2020-09-19 14:24 ` bug#43501: Whitelisting/blacklisting transitive package dependencies Danny Milosavljevic
2020-09-20 22:00 ` Mark H Weaver [this message]
2020-09-22 2:36 ` bug#43501: gst-plugins-bad cannot be built on linux-armhf, breaking qemu 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
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=87zh5kw1k7.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 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).