New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/34904#issuecomment-1074061880

Comment:
The issue isn't how `wireplumber` gets launched, but how it is built. We cannot have the `wireplumber` package depend on `pipewire` and the `pipewire` package depend on `wireplumber` because that creates a build cycle.

If it is ugly to build `wireplumber` as part of the `pipewire` package (I have an unverified suspicion that it may be), it may be less ugly to have a `pipewire-bootstrap` package or something that can satisfy the `makedepends` and `checkdepends` of `pipewire` to break the cycle. I am not attuned enough to `pipewire` to have an opinion here.

Of course, if `wireplumber` is to be a new, official replacement for the old session manager, it seems that upstream should provide a clean way to build the entire apparatus together, such as by pulling `wireplumber` into the source tree. It is **always** problematic to say "you need package X to build package Y, but you need package Y to run package X".

Cf. the nightmare that is PEP-517 build systems which depend on an external TOML parser.