I'm not going to consider PIPEWIRE or any other option for KDE ports until it supported upstream. Moreover, in kde@ we often don't even make options for ports when they are supported upstream and the reason is plain simple: we do not have enough time and manpower to maintain all possible combination of options for a huge chunk software like KDE ports.

This is not just some build option - it is an opportunity to get rid of unnecessary bloatware in the system (like pulseaudio or avahi).

Discussion with upstream: https://bugs.kde.org/show_bug.cgi?id=499828

In D49009#1118524, @makc wrote:

Discussion with upstream: https://bugs.kde.org/show_bug.cgi?id=499828

The link contains a discussion (+patch) of the possibility of build and work spectacle without pipewire. Unlike spectacle, the ports mentioned in this review can be build and run without pipewire, but for some reason this dependency was made mandatory in the ports.

Rather than patching all kpipewire consumers I'd prefer a patch for kpipewire itself that makes it a stub.