From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gst-plugins-base1: break cycle by making libvisual dependency optional
Date: Tue, 11 Feb 2025 14:49:44 +0100 [thread overview]
Message-ID: <20250211134944.6E3142B046@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54218@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
There's a merged pull request on the void-packages repository
gst-plugins-base1: break cycle by making libvisual dependency optional
https://github.com/void-linux/void-packages/pull/54218
Description:
Closes: #54215
#### Testing the changes
- I tested the changes in this PR: **NO**
I have no idea if the absence of this plugin breaks any packages as we ship them, or how many people's workflows will be disrupted, but cutting `libvisual` out of the loop seems to be the easiest way to break a dependency cycle.
cc: @Piraty
next prev parent reply other threads:[~2025-02-11 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 19:10 [PR PATCH] " ahesford
2025-02-04 19:10 ` [PR PATCH] [Updated] " ahesford
2025-02-11 13:49 ` ahesford [this message]
2025-02-11 13:55 ` Piraty
2025-02-11 14:04 ` hartwork
2025-02-11 14:04 ` hartwork
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=20250211134944.6E3142B046@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).