-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PipeWire multi-arch cross-build Discussion #67
Comments
If you're limited on time, I'd suggest focusing on amd64. A reasonable goal is to provide the latest PipeWire and associated libraries and tools for a large population of eager testers, and this can also help upstream to get better test coverage across usage patterns and equipment. More exotic architectures are left to upgrade their system e.g. Debian unstable. Another policy would be to do like Debian, disable certain features for some architectures. This means you're spending minimal time on these other architectures, and many architectures are supported almost at no extra effort. Seems like a good compromise to me. Trying to keep everything consistent across all architectures would require a lot of upstream work. |
Yeah, I also thought like this. Its better to have a compromised pipewire other than nothing for other archs. As you can see as of now our PPA is ready to accept other architecture we can do for pipewire also with trimmed features. Yeah have less time, but you can even give some MR for this 😅 otherwise it will take time for me. |
* Initial Support to multi-arch see: #67 Debian Package - - move out pipewire-media-session to a new package - move out pipewire-x11-bell to a new package (=> NEW) - Recommending using wireplumber. add ppa : ppa:pipewire-debian/wireplumber-upstream - Recommending rt-kit and dbus-session-managers PipeWire - - Add 44.1KHz to allowed samplerates. The server can now switch by default between 48KHz and 44.1KHz. - Streams now allocate less resources. - Fix some bugs that could make the server crash. - Bluetooth now supports the LC3plus vendor codec. - Many bugfixes and improvements. - For more : https://gitlab.freedesktop.org/pipewire/pipewire/-/releases . . . . Upstream recommends to use 'WirePlumber' instead 'pipewire-media-session' to get it add another PPA, 'sudo add-apt-repository ppa:pipewire-debian/wireplumber-upstream' For more instruction read : https://pipewire-debian.github.io . . ok
* Now can be built with * amd64 * arm64 * armhf * i386 * ppc64el * s390x For more and participate in Discussion, please see : #67
Hi @tormodvolden |
* Initial Support to multi-arch see: #67 Debian Package - - move out pipewire-media-session to a new package - move out pipewire-x11-bell to a new package (=> NEW) - Recommending using wireplumber. add ppa : ppa:pipewire-debian/wireplumber-upstream - Recommending rt-kit and dbus-session-managers PipeWire - - Add 44.1KHz to allowed samplerates. The server can now switch by default between 48KHz and 44.1KHz. - Streams now allocate less resources. - Fix some bugs that could make the server crash. - Bluetooth now supports the LC3plus vendor codec. - Many bugfixes and improvements. - For more : https://gitlab.freedesktop.org/pipewire/pipewire/-/releases . . . . Upstream recommends to use 'WirePlumber' instead 'pipewire-media-session' to get it add another PPA, 'sudo add-apt-repository ppa:pipewire-debian/wireplumber-upstream' For more instruction read : https://pipewire-debian.github.io . .
* Now can be built with * amd64 * arm64 * armhf * i386 * ppc64el * s390x For more and participate in Discussion, please see : #67
I landed here because I needed extended Pipewire tooling on Debian, like in the repo name... Apparently, Ubuntu dpkg supports a compression algorithm that Debian dpkg does not => https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892664 I get Maybe while adjusting for multiple architectures, you could also downgrade the compression so the packages are actually installable on Debian ? |
@DanceMore which version of ubuntu are you using for debain unstable ? for only blueman you can use https://github.com/blueman-project/blueman/wiki/Packaged-versions for now. I will fix this in next version https://stackoverflow.com/a/72359798 |
See #64
@tormodvolden
The text was updated successfully, but these errors were encountered: