It would be nice if media-sound/mumble-1.2.0 could be slotted, so Mumble 1.1 and Mumble 1.2 can be installed in parallel. Their network protocols are incompatible, so some way of having both installed is definitely necessary. Maybe a path to avoid colliding files has to be developed, thus it would be best to work that out early (before final release) with upstream devs. Reproducible: Always
Upstream afaik includes a newer snapshot of 1.1 in the 1.2 sources. (Or at least that was the plan, which is currently executed for Windows builds already.)
Build of mumble11x binary is disabled in the 1.2.0_beta1 ebuild... Why disable it by default ? couldn't it depend on some useflag ? Or as it is asked above, maybe mumble should be slotted. All servers are not going to migrate immediately to 1.2.0 so this is quite annoying.
Created attachment 211535 [details] Ebuild with compatibility client I've attached an ebuild which builds the 1.1.x compatibility client when USE="11x" is active (on by default). Upstream has said that they will remove the compatibility client from the installer (and probably the source package as well) once the install base of the new version grows, and if/when that happens it might be best to include the 11x client as it's own package. But for now this feels like a better option.
Renaming that ebuild to 1.2.0 works fine for me. Now I have both mumble and mumble11x. Thanks.
I also need this use flag to use "mumble11x".
Created attachment 216066 [details] Ebuild with compatibility client
It would be nice to have this USE flag in the official ebuild. Without it is not possible to connect to many servers which are using the older protocol version.
In the meantime upstream has dropped the old legacy client, so I'm closing this as wontfix. If you still rely on it I suggest keeping it in a local overlay.
