Ophestra 503bfc6468

internal/system: port connect by name ...

This behaviour is a bit messy and checks what appears to be a windows-specific environment variable for some reason. Keeping everything intact regardless to match upstream behaviour.

Signed-off-by: Ophestra <cat@gensokyo.uk>

2025-12-07 02:00:19 +09:00

..

testdata

internal/pipewire: store sample iovec continuously

2025-11-28 00:35:10 +09:00

client_test.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00

client.go

internal/pipewire: collect non-protocol errors

2025-12-03 01:35:43 +09:00

core_test.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00

core.go

internal/pipewire: check pending ids after done

2025-12-06 21:09:55 +09:00

header_test.go

internal/pipewire: implement Core::Error

2025-11-30 01:39:39 +09:00

header.go

internal/pipewire: implement client context

2025-12-02 06:03:21 +09:00

pipewire_test.go

internal/pipewire: use sendmsg/recvmsg directly

2025-12-06 02:12:47 +09:00

pipewire.go

internal/system: port connect by name

2025-12-07 02:00:19 +09:00

pod_test.go

internal/pipewire: improve protocol error messages

2025-12-04 03:15:58 +09:00

pod.go

internal/pipewire: improve protocol error messages

2025-12-04 03:15:58 +09:00

securitycontext_test.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00

securitycontext.go

internal/pipewire: high level SecurityContext helper

2025-12-06 21:16:27 +09:00

spa_test.go

internal/pipewire: use type name in error strings

2025-12-04 02:29:27 +09:00

spa.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00