From: Zhu Zihao <all_but_last@163.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 54744@debbugs.gnu.org
Subject: [bug#54744] [PATCH] Update gstreamer and its families to 1.20.1.
Date: Wed, 06 Apr 2022 17:16:54 +0800 [thread overview]
Message-ID: <86czhud07t.fsf@163.com> (raw)
In-Reply-To: <2a54af688cb50fc4bdaa96650be5718d12d420f0.camel@ist.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 2499 bytes --]
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
>> * gnu/packages/gstreamer.scm (%gstreamer-version): New variable.
> I don't think that's necessary or even beneficial. Drop it.
> Ditto for all the packages referencing it.
Good. From my view this can ensure packager to update every package of
gstreamer, not only a part of them. Gstreamer now use a monorepo for all
its components, they'll also have regular release cycle for all
components.
>> * gnu/packages/gstreamer.scm (gst-plugins-good): Update to 1.20.1.
>> [...]
>> [propagated-inputs]: Remove unnecessary propagation.
> Do gst-plugins-good really no longer depend on the base plugins?
>
>> * gnu/packages/gstreamer.scm (gst-plugins-ugly): Update to 1.20.1.
>> [...]
>> [propagated-inputs]: Remove unnecessary propagation.
> Idem.
>
>> * gnu/packages/gstreamer.scm (gst-libav): Update to 1.20.1.
>> [...]
>> [propagated-inputs]: Remove unnecessary propagation.
> Ibidem.
I checked the ugly and good and gst-libav, they do rely on
gst-plugins-base, but no propagation needed. I don't find a reason that
they really requires propagation, because their content just a so file.
Gstreamer in Nixpkgs also don't have propagations for above packages.
For necessary propgations like gst-plugins-bad(header or gi), I've added
some comments.
>> (gst-plugins/selection): Remove because it's not useful in packaging
>> and requires extra maintenance.
>> * gnu/packages/video.scm (pitivi)[inputs]: Use gst-plugins-bad.
> Packages that only require some bad plugins and can exactly state which
> should not be forced to pull in all of them. The bad plugins are
> explicitly named bad, because they're bad. Enabling any of them beyond
> necessity should be an active choice of the user.
>
>> * gnu/packages/webkit.scm (webkitgtk):
>> [inputs]: Add gst-plugins-bad. It provides gstreamer-parsecodec.
> My, what a perfect use case for gst-plugins/selection that would be.
> Note, that gratuitous media codecs are an additional attack surface.
>
> Cheers
I'll investigate into it.
Currently I only see pitivi use gst-plugins/selection. Many package use
gst-plugins-bad directly.
BTW, how to maintain changes for a long patches series like this in the
review phase? It's quite annoying when I make some minor changes but I
have to re-sent all patches to the mail list.
--
Retrieve my PGP public key:
gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-04-06 9:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 3:38 [bug#54744] [PATCH] Update gstreamer and its families to 1.20.1 Zhu Zihao
2022-04-06 5:56 ` Liliana Marie Prikler
2022-04-06 9:16 ` Zhu Zihao [this message]
2022-04-06 10:05 ` Liliana Marie Prikler
2022-04-06 15:34 ` Zhu Zihao
2022-04-07 6:27 ` Liliana Marie Prikler
2022-06-26 17:17 ` [bug#54744] [PATCH staging v2 01/20] gnu: python-gst: Add upstream-name Liliana Marie Prikler
2022-06-26 17:22 ` [bug#54744] [PATCH staging v2 02/20] gnu: gstreamer: Update to 1.20.3 Liliana Marie Prikler
2022-06-26 17:22 ` [bug#54744] [PATCH staging v2 03/20] gnu: gst-plugins-base: " Liliana Marie Prikler
2022-06-26 17:23 ` [bug#54744] [PATCH staging v2 04/20] gnu: gst-plugins-good: " Liliana Marie Prikler
2022-06-26 17:25 ` [bug#54744] [PATCH staging v2 05/20] gnu: gst-plugins-bad: " Liliana Marie Prikler
2022-06-26 17:25 ` [bug#54744] [PATCH staging v2 06/20] gnu: gst-plugins-ugly: " Liliana Marie Prikler
2022-06-26 17:25 ` [bug#54744] [PATCH staging v2 07/20] gnu: gst-libav: " Liliana Marie Prikler
2022-06-26 17:25 ` [bug#54744] [PATCH staging v2 08/20] gnu: gst-editing-services: " Liliana Marie Prikler
2022-06-26 17:26 ` [bug#54744] [PATCH staging v2 09/20] gnu: gstreamer-docs: " Liliana Marie Prikler
2022-06-26 17:26 ` [bug#54744] [PATCH staging v2 10/20] gnu: python-gst: " Liliana Marie Prikler
2022-06-28 18:41 ` [bug#54744] [PATCH staging v2 11/20] gnu: gst-plugins/selection: Implement in terms of G-Expressions Liliana Marie Prikler
2022-06-28 18:59 ` [bug#54744] [PATCH staging v2 12/20] gnu: Add gst-plugins-bad-minimal Liliana Marie Prikler
2022-06-28 19:19 ` [bug#54744] [PATCH staging v2 13/20] gnu: webkitgtk: Add missing inputs Liliana Marie Prikler
2022-06-29 19:15 ` [bug#54744] [PATCH staging v2 14/20] gnu: gstreamer: Use new package style Liliana Marie Prikler
2022-06-29 19:17 ` [bug#54744] [PATCH staging v2 15/20] gnu: gst-plugins-good: " Liliana Marie Prikler
2022-06-29 19:18 ` [bug#54744] [PATCH staging v2 16/20] gnu: gst-plugins-bad: " Liliana Marie Prikler
2022-06-29 19:19 ` [bug#54744] [PATCH staging v2 17/20] gnu: gst-plugins-ugly: " Liliana Marie Prikler
2022-06-29 19:20 ` [bug#54744] [PATCH staging v2 18/20] gnu: gst-editing-services: " Liliana Marie Prikler
2022-06-29 19:20 ` [bug#54744] [PATCH staging v2 19/20] gnu: gst-python: " Liliana Marie Prikler
2022-06-30 4:14 ` [bug#54744] [PATCH staging v2 20/20] gnu: gst-editing-services: Update FIXME comment Liliana Marie Prikler
2022-06-30 16:55 ` [bug#54744] [PATCH staging v2 00/20] Update gstreamer et al. to 1.20.3 Liliana Marie Prikler
2022-07-03 7:28 ` Zhu Zihao
2022-07-31 10:19 ` bug#54744: " 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=86czhud07t.fsf@163.com \
--to=all_but_last@163.com \
--cc=54744@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/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).