Package Details: pipewire-common-x11-bell-git 1.0.0.r591.gaf310523-1

Git Clone URL: https://aur.archlinux.org/pipewire-common-git.git (read-only, click to copy)
Package Base: pipewire-common-git
Description: Low-latency audio/video router and processor - X11 bell
Upstream URL: https://pipewire.org
Licenses: MIT
Conflicts: pipewire-x11-bell
Provides: pipewire-x11-bell
Submitter: eh5
Maintainer: eh5
Last Packager: eh5
Votes: 5
Popularity: 0.000000
First Submitted: 2021-01-10 08:40 (UTC)
Last Updated: 2024-03-29 06:17 (UTC)

Pinned Comments

PedroHLC commented on 2021-01-11 22:53 (UTC)

If someone needs any of these packages pre-built, chaotic-aur builds them hourly...

eh5 commented on 2021-01-10 12:03 (UTC) (edited on 2021-01-16 20:46 (UTC) by eh5)

@FabioLolix This one has gstreamer support (provides gst-plugin-pipewire) and hsphfpd support enabled.

(All below is edit message for anyone who interests.)

Be aware that https://aur.archlinux.org/packages/gst-plugin-pipewire-git/ depend by pipewire-git is not part of pipewire-git package base.

Many people request[1-2] the maintainer(https://aur.archlinux.org/account/sl1pkn07) of pipewire-git to enable gstreamer support but seems he refuse to do that. Despite gstreamer support is enabled by default in upstream (also in Arch repo) and gstreamer plugin is a dynamic loadable library which is capable to be split into separate package.

And some request to orphan or delete pipewire-git but all has been rejected by TU[3].

There was a VCS package solved gstreamer problem named pipewire-nightly, but a TU decides to delete it for the reason that the suffix "-nightly" in package name imply that it has to be a snapshot package[4].

Those are reasons why I create this package base.

[1] https://aur.archlinux.org/pkgbase/pipewire-git/?O=20&PP=10#comment-775875

[2] https://aur.archlinux.org/pkgbase/pipewire-git/?O=10&PP=10#comment-777463

[3] https://lists.archlinux.org/pipermail/aur-requests/2020-December/thread.html (search keyword "pipewire")

[4] https://lists.archlinux.org/pipermail/aur-requests/2020-December/047836.html

Latest Comments

1 2 3 4 5 6 Next › Last »

muflone commented on 2024-02-10 19:01 (UTC)

@eh5 I pinned your comment linked in both the previous comments and the aur-requests mailing list as the used link was broken

Kunda commented on 2023-12-02 23:22 (UTC)

1.7.1 released https://github.com/sonosaurus/sonobus/releases/tag/1.7.1

eh5 commented on 2023-11-24 00:32 (UTC)

Currently broken due to requiring roc-toolkit>=0.3.0. As there is no working roc-toolkit package in AUR, please wait Arch developer to roll out roc-toolkit 0.3.0 .

eh5 commented on 2022-12-31 07:35 (UTC)

@leny

You need to force install libcamera 0.0.3-1 with pacman -Sdd libcamera and then rebuild pipewire-common-git.

It's recommended to build pipewire-common-git in chroot so you can avoid these hassles. Or just install pipewire-common-git from chaotic-aur repo mentioned in the pinned comment.

leny commented on 2022-12-30 13:57 (UTC)

Latest libcamera is conflicting with pipewire packages:

:: installing libcamera (0.0.3-1) breaks dependency 'libcamera-base.so=0.0.2-64' required by pipewire-common-git
:: installing libcamera (0.0.3-1) breaks dependency 'libcamera.so=0.0.2-64' required by pipewire-common-git

souravdas142 commented on 2022-05-07 14:23 (UTC) (edited on 2022-05-07 14:27 (UTC) by souravdas142)

lc3plus codec is here (If any packager @eh5 wants to package) : https://www.etsi.org/deliver/etsi_ts/103600_103699/103634/01.03.01_60/

for

-D bluez5-codec-lc3plus=enabled

eh5 commented on 2022-04-08 17:57 (UTC)

Noticed you are a TU, here is a short explanation on why I created pipewire-common-git https://aur.archlinux.org/pkgbase/pipewire-common-git#comment-785408 .

eh5 commented on 2022-04-08 17:51 (UTC) (edited on 2022-04-08 17:51 (UTC) by eh5)

@dvzrv The PKGBUILD of this this pkgbase build the latest version(git master branch) of pipewire.

The "common" in package name is just to distinguish from another AUR package of pipewire, "pipewire-git".

dvzrv commented on 2022-04-08 17:45 (UTC)

@eh5: What is the use-case for this package in comparison to the extra/pipewire split-package?