From: excalamus--- via <help-guix@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Playing video in browser
Date: Thu, 4 Jun 2020 23:36:48 +0200 (CEST) [thread overview]
Message-ID: <M9017CF--3-2@tutanota.com> (raw)
In-Reply-To: <87367ar57t.fsf@ambrevar.xyz>
Jun 4, 2020, 15:39 by mail@ambrevar.xyz:
> It's not very obvious what to document it since it applies to all
> WebKitGTK.
>
One idea is to indicate the relationship between packages. For example,
guix package -s gstreamer | less
...
+ Applications can take advantage of advances in codec and filter technology
+ transparently. Developers can add new codecs and filters by writing a simple
+ plugin with a clean, generic interface.
+
+ This package provides the core library and elements. <new>See gst-plugins-* for additional codecs, filters, and functionality.</new>
Another is to describe an end-user's perspective of the gst-plugins-*. The description taken from GStreamer focuses on licensing and is developer-centric. It's unclear as a user that the plugins may solve my problem. Maybe something like,
guix package -s gst-plugins-ugly | less
...
+ description: GStreamer Ugly Plug-ins <new>for extra codecs, filters, and functionality</new>. This set contains those plug-ins which
+ the developers consider to have good quality code but that might pose
+ distribution problems in some jurisdictions, e.g. due to patent threats.
> It's part of the "general software knowledge". For instance, if you
> install an archiver like `atool', it's your reponsibility to install the
> backends (unzip, p7zip, etc.) to support the various archive formats.
> Where to document this? I don't know, but it's unclear that Guix is the
> place.
>
I follow you. Some tools, like `atool`, make that responsibility clear in their documentation. Unfortunately, GStreamer is not as clear. That's an upstream issue.
Guix could help users by providing a recipe or a ready-to-use package.
Is the Guix Cookbook not an appropriate place for a tutorial on setting up a Guix System for general web viewing? This seems within Guix's purview.
I couldn't find a webviewer through Guix which allowed me to view the Guix videos out-of-the-box.
I'm happy to help with any of these.
next prev parent reply other threads:[~2020-06-04 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 15:36 Playing video in browser excalamus--- via
2020-06-04 15:59 ` Pierre Neidhardt
2020-06-04 16:52 ` excalamus--- via
2020-06-04 19:39 ` Pierre Neidhardt
2020-06-04 21:36 ` excalamus--- via [this message]
2020-07-08 10:40 ` Pierre Neidhardt
2020-06-05 20:53 ` Where to document package relations (was: Playing video in browser) Dmitry Alexandrov
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=M9017CF--3-2@tutanota.com \
--to=help-guix@gnu.org \
--cc=excalamus@tutanota.com \
--cc=mail@ambrevar.xyz \
/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.
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).