New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/38521#issuecomment-1403743362

Comment:
It is pretty clear that upstream does not want people running p-m-s anymore:

> https://gitlab.freedesktop.org/pipewire/media-session/-/releases/0.4.2

I don't think p-m-s should be split into a subpackage; it should just be dropped with the (next) release of pipewire. At the very least, this means we should probably tack on an install message *now* to warn people that this will happen. 

Wireplumber shouldn't depend on pipewire; in fact, the dependency should be the other way around when p-m-s is no longer an option (unless we have an alternative session manager packaged). Having the proper dependency relationship should minimize the pain of transition for users with the default configuration, but it creates a build cycle that we will have to break. Options include:
- Renaming pipewire to something like `pipewire-tools` or `pipewire-utils` and adding a standalone `pipewire` meta-package that pulls in `pipewire-tools` as well as `wireplumber`. This has the advantage that we don't really have to worry about syncing the build process between two artificially split packages. In fact, the meta can just get a dated version that we only bump when we need to.
- Alternatively, `libpipewire` and `pipewire-devel` could be split into a standalone package so that `wireplumber` can pull them in without the rest. This kind of sucks because we'll be forced to keep two packages synchronized. 
- Coming up with some way to build `wireplumber` without the `pipewire-devel` dependency. Meh.