George Kiagiadakis authored Apr 28, 2021 and Julian Bouzas committed May 13, 2021

These are also printed by libpipewire on the DEBUG level
and they are really not that harmful, so we don't need to spam
users with "failed" messages and alarm them

George Kiagiadakis authored Apr 28, 2021 and Julian Bouzas committed May 13, 2021

Add a unit test for this. Create a link with invalid nodes and expect
the activation transition to error out.

the "long" type in spa-pod is int64_t, so we need to make sure we
pass a 64-bit number there, otherwise the va_args is going to crash
on some architectures while reading arguments off the stack

Fixes some issues for 32bit architectures

The policy scripts can handle now client nodes that want to be linked with other
client nodes. This is needed for nodes created by the Pulse Audio Volume Control
to monitor audio comming from other application client nodes.

Not really a hard requirement, wrt libpipewire API, but it's
hard to keep runtime compatibility with earlier versions when
it comes to configuration options

Plugin() is confusing because it's not a constructor, it just finds
an existing instance of a plugin object. All other camel-case
functions are constructors in the current lua API.

This is no longer used and likely not very useful now that we have
a simpler design.
We can re-add it in the future if necessary, but let's keep it out
of the 0.4 release.

Also rename the intermediate lua api table WpDebug -> WpLog

Keeps things more consistent with the function names (wp_log*),
with the lua api (Log.*) and with pipewire using log.{h,c} as well.
After all, these functions are for logging...

This is not part of the policy, it's something standalone that writes metadata

Needs to be disabled by default, since it's not built by default now

We no longer have the audiofade-related code

This is only intended to be used with specific embedded
applications. There is no good reason to use it on
a standard desktop environment.