[gentoo-dev] [PATCH v2] 2024-05-03-wireplumber-0_5-bump: add news item

[gentoo-dev] [PATCH v2] 2024-05-03-wireplumber-0_5-bump: add news item

[James Calligeros]

Signed-off-by: James Calligeros <jcalligeros99@gmail.com>
---
 .../2024-05-03-wireplumber-0_5-bump.en.txt    | 25 +++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt

diff --git a/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt b/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt
new file mode 100644
index 0000000..22f2314
--- /dev/null
+++ b/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt
@@ -0,0 +1,25 @@
+Title: media-video/wireplumber-0.5.2 may break on upgrade
+Author: James Calligeros <jcalligeros99@gmail.com>
+Posted: 2024-05-03
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: media-video/wireplumber
+
+As some will be aware, WirePlumber 0.5.0 introduced a significant
+breaking change to its entire configuration system, eliminating the use
+of Lua scripts for configuration purposes. This also came with a
+complete rework of how Lua scripts are registered with WirePlumber
+for execution.
+
+Most typical desktop users, including EasyEffects users, should not
+notice any change to their system. That said, it was not uncommon for
+people to suggest or implement configuration changes using the Lua API.
+
+Any custom functionality which relies on WirePlumber's Lua API will
+break upon upgrade.
+
+If you rely on this functionality, please review the WirePlumber
+documentation on porting your Lua scripts to the new API and
+registering them with the system before upgrading:
+
+https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/migration.html
-- 
2.45.0

Re: [gentoo-dev] [PATCH v2] 2024-05-03-wireplumber-0_5-bump: add news item

[Sam James]

James Calligeros <jcalligeros99@gmail.com> writes:

> Signed-off-by: James Calligeros <jcalligeros99@gmail.com>
> ---
>  .../2024-05-03-wireplumber-0_5-bump.en.txt    | 25 +++++++++++++++++++
>  1 file changed, 25 insertions(+)
>  create mode 100644 2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt
>
> diff --git a/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt b/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt
> new file mode 100644
> index 0000000..22f2314
> --- /dev/null
> +++ b/2024-05-03-wireplumber-0_5-bump/2024-05-03-wireplumber-0_5-bump.en.txt
> @@ -0,0 +1,25 @@
> +Title: media-video/wireplumber-0.5.2 may break on upgrade
> +Author: James Calligeros <jcalligeros99@gmail.com>
> +Posted: 2024-05-03
> +Revision: 1
> +News-Item-Format: 2.0
> +Display-If-Installed: media-video/wireplumber
> +
> +As some will be aware, WirePlumber 0.5.0 introduced a significant
> +breaking change to its entire configuration system, eliminating the use
> +of Lua scripts for configuration purposes. This also came with a
> +complete rework of how Lua scripts are registered with WirePlumber
> +for execution.
> +
> +Most typical desktop users, including EasyEffects users, should not
> +notice any change to their system. That said, it was not uncommon for
> +people to suggest or implement configuration changes using the Lua API.
> +
> +Any custom functionality which relies on WirePlumber's Lua API will
> +break upon upgrade.
> +
> +If you rely on this functionality, please review the WirePlumber
> +documentation on porting your Lua scripts to the new API and
> +registering them with the system before upgrading:
> +
> +https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/migration.html

LGTM. Let's give it the standard 48 hours then let's ship it.

If you feel it'd be useful to commit pw+wp masked before then, we can,
but my gut is that it isn't.

Thanks again for working on this.

best,
sam

Re: [gentoo-dev] [PATCH v2] 2024-05-03-wireplumber-0_5-bump: add news item

[James Calligeros]

On Sat, May 4, 2024 at 1:30 PM Sam James <sam@gentoo.org> wrote:

> If you feel it'd be useful to commit pw+wp masked before then, we can,
> but my gut is that it isn't.

I see no reason to do so either.

> Thanks again for working on this.

No worries at all :)

> best,
> sam

Regards,

James