From: Pierre Neidhardt <mail@ambrevar.xyz>
To: 42262@debbugs.gnu.org
Subject: [bug#42262] [PATCH 4/6] gnu: gst-plugins-bad: Describe where these plugins are useful.
Date: Wed, 8 Jul 2020 12:28:45 +0200 [thread overview]
Message-ID: <20200708102847.32156-3-mail@ambrevar.xyz> (raw)
In-Reply-To: <20200708102847.32156-1-mail@ambrevar.xyz>
* gnu/packages/gstreamer.scm (gst-plugins-bad)[description]: Explain that
this plugin can be used to play videos, e.g. in a web browser.
---
gnu/packages/gstreamer.scm | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/gstreamer.scm b/gnu/packages/gstreamer.scm
index de9219bb75..3651cf7329 100644
--- a/gnu/packages/gstreamer.scm
+++ b/gnu/packages/gstreamer.scm
@@ -426,8 +426,10 @@ quality code and correct functionality.")
(home-page "https://gstreamer.freedesktop.org/")
(synopsis "Plugins for the GStreamer multimedia library")
(description
- "GStreamer Bad Plug-ins is a set of plug-ins whose quality aren't up to
-par compared to the rest.")
+ "GStreamer Bad Plug-ins are extra codecs, filters, and functionality that
+are can be used for media playback in external applications like web browsers.
+
+The quality of this set of plug-ins isn't up to par compared to the rest.")
(license license:lgpl2.0+)))
(define-public gst-plugins-ugly
--
2.27.0
next prev parent reply other threads:[~2020-07-08 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 10:27 [bug#42262] [PATCH 1/6] gnu: webkitgtk: Refer to GStreamer plugins in description Pierre Neidhardt
2020-07-08 10:28 ` [bug#42262] [PATCH 2/6] gnu: gstreamer: " Pierre Neidhardt
2020-07-08 10:28 ` [bug#42262] [PATCH 3/6] gnu: gst-plugins-good: Describe where these plugins are useful Pierre Neidhardt
2020-07-08 10:28 ` Pierre Neidhardt [this message]
2020-07-08 10:28 ` [bug#42262] [PATCH 5/6] gnu: gst-plugins-ugly: " Pierre Neidhardt
2020-07-08 10:28 ` [bug#42262] [PATCH 6/6] gnu: gst-libav: " Pierre Neidhardt
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=20200708102847.32156-3-mail@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=42262@debbugs.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.