You are not logged in.

#1 2021-02-26 06:57:03

meister1593
Member
Registered: 2021-02-26
Posts: 2

Considering making group or meta package for pipewire

I thought it would be convenient to have group for pipewire packages, since one  it's packages aren't clearly pipewire-named and having such group would make installing whole pipewire suite easier.

Specifically, pipewire group/meta package should contain:
pipewire
pipewire-docs
pipewire-jack
pipewire-alsa
pipewire-pulse
pipewire-ffmpeg
alsa-card-profiles

Offline

#2 2021-02-26 10:06:15

Omar007
Member
Registered: 2015-04-09
Posts: 367

Re: Considering making group or meta package for pipewire

This is pretty much already the case though. The pipewire package is basically the meta-package you're talking about; if you install pipewire, the mentioned packages are either a required dependency or an optional dependency.

In contrast to some other package managers, pacman doesn't automatically install optional dependencies and doesn't (currently?) have a flag to forcibly install them all. Installation of the optional dependencies would depend on your desired setup and are only provided as an informational message by pacman.
If you're looking for something that forcibly installs and enables all of the optional dependencies of a given package, that doesn't really exist in the Arch eco-system at the moment. Not to mention that even if/when some of the optional dependencies are installed, they may still need manual actions to actually be enabled/used. In the case of pipewire, this used to be relevant for pipewire-pulse and is currently still relevant for pipewire-jack afaik.

Also, two small sidenotes;
1) your pipewire-ffmpeg link doesn't exist/go anywhere but if/when it does, it'd also be a fine optional dependency
2) you missed the gstreamer plugin (which is luckily also properly marked as optdepend so when you install pipewire, you'll be notified  wink )


For reference.
https://github.com/archlinux/svntogit-p … GBUILD#L54

depends=(rtkit alsa-card-profiles libdbus-1.so libncursesw.so libsndfile.so
           libudev.so libasound.so libsystemd.so libbluetooth.so libsbc.so
           libldacBT_enc.so libopenaptx.so libfdk-aac.so)
optdepends=('pipewire-docs: Documentation'
              'pipewire-alsa: ALSA configuration'
              'pipewire-jack: JACK support'
              'pipewire-pulse: PulseAudio replacement'
              'gst-plugin-pipewire: GStreamer support'
)

Last edited by Omar007 (2021-02-26 10:09:18)

Offline

#3 2021-02-26 14:35:04

meister1593
Member
Registered: 2021-02-26
Posts: 2

Re: Considering making group or meta package for pipewire

Omar007 wrote:

This is pretty much already the case though. The pipewire package is basically the meta-package you're talking about; if you install pipewire, the mentioned packages are either a required dependency or an optional dependency.

In contrast to some other package managers, pacman doesn't automatically install optional dependencies and doesn't (currently?) have a flag to forcibly install them all. Installation of the optional dependencies would depend on your desired setup and are only provided as an informational message by pacman.
If you're looking for something that forcibly installs and enables all of the optional dependencies of a given package, that doesn't really exist in the Arch eco-system at the moment. Not to mention that even if/when some of the optional dependencies are installed, they may still need manual actions to actually be enabled/used. In the case of pipewire, this used to be relevant for pipewire-pulse and is currently still relevant for pipewire-jack afaik.

Also, two small sidenotes;
1) your pipewire-ffmpeg link doesn't exist/go anywhere but if/when it does, it'd also be a fine optional dependency
2) you missed the gstreamer plugin (which is luckily also properly marked as optdepend so when you install pipewire, you'll be notified  wink )


For reference.
https://github.com/archlinux/svntogit-p … GBUILD#L54

depends=(rtkit alsa-card-profiles libdbus-1.so libncursesw.so libsndfile.so
           libudev.so libasound.so libsystemd.so libbluetooth.so libsbc.so
           libldacBT_enc.so libopenaptx.so libfdk-aac.so)
optdepends=('pipewire-docs: Documentation'
              'pipewire-alsa: ALSA configuration'
              'pipewire-jack: JACK support'
              'pipewire-pulse: PulseAudio replacement'
              'gst-plugin-pipewire: GStreamer support'
)

Ah yes, i didn't notice optdepends, i thought more about one-group solution to install everything at once.

About packages, i used this aur package for reference, missed gst plugin completely.

Also, this pkgbuild provides ffmpeg plugin, which is named as "FFmpeg SPA plugin". Does it exist in repository?

Offline

#4 2021-02-26 14:54:49

Omar007
Member
Registered: 2015-04-09
Posts: 367

Re: Considering making group or meta package for pipewire

The ffmpeg SPA plugin does not exist in the repositories. It is disabled by default upstream and as such it also isn't being build for Arch, thus not in the repositories.

You could submit a request for it to be enabled in the Arch package if that hasn't been done already (check if something exists on the subject before you submit the request!).

Offline

Board footer

Powered by FluxBB