Package Details: apulse-git 0.1.12_r5_gbcd55c8-1

Git Clone URL: (read-only, click to copy)
Package Base: apulse-git
Description: Pulseaudio emulation for ALSA
Upstream URL:
Licenses: MIT
Conflicts: apulse
Provides: apulse
Submitter: WorMzy
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 11
Popularity: 0.000000
First Submitted: 2014-09-21 00:26 (UTC)
Last Updated: 2019-02-01 20:23 (UTC)

Required by (2)

Sources (1)

Latest Comments

1 2 3 Next › Last »

WorMzy commented on 2022-06-17 10:59 (UTC)

It may be unmaintained upstream, but if it's still usable then I don't see a need for deletion. Pipewire may well be capable of replacing pulseaudio, but I don't see why ALSA-only users would be inclined to use that.

MarsSeed commented on 2022-06-17 10:54 (UTC)

According to the developer, this project isn't maintained since 2015:

Issue: #121: Is this project unmaintained?

I think it's best to delete this package. We now have PipeWire that can supersede PulseAudio and which implements its own PulseAudio compatibility interface with great efficiency and convenience.

PipeWire developmet has strong community and corporate backing, whereas this was essentially a one-person project.

WorMzy commented on 2017-06-18 15:38 (UTC)

Done. :)

Lone_Wolf commented on 2017-06-18 12:24 (UTC)

Please add a conflict with apulse

Ralf_Mardorf commented on 2017-03-08 20:55 (UTC)

I send a request.

Ralf_Mardorf commented on 2017-03-08 20:44 (UTC) (edited on 2017-03-08 20:58 (UTC) by Ralf_Mardorf)

You are mistaken. I recommend you sent a request to the AUR general mailing list. However, I'm not an AUR keeper, feel free to ignore conformity.

WorMzy commented on 2017-03-08 20:02 (UTC)

As I said -- periods and underslashes are treated the same as each other by pacman. Using one or the other is just preference, and I prefer the latter (as it makes it clear where the "release" string ends, and the revision/hash begins). The pkgver extracts on the wiki are not there as strict rules that you need to comply with, but simply as examples that produce good, incrementing pkgvers.

Ralf_Mardorf commented on 2017-03-08 18:55 (UTC)

No, it's the "r" as well as the dots. I'm not the AUR police, but some compliance doesn't harm. In this case I'm against an epoch, too, for more or less the same reasons as already mentioned by the maintainer.

SanskritFritz commented on 2017-03-08 18:12 (UTC)

Fair enough, it's your package after all. Thanks!

WorMzy commented on 2017-03-08 16:08 (UTC)

If the build changes, I update the PKGBUILD and the pkgver gets bumped. There may even be a comment, so enable notifications. Chances are though, if the build process needs changing, then outdated PKGBUILDs will stop working anyway. If you want to be on the safe side, always download the snapshot/git pull from the AUR before rebuilding, don't rely on local copies of build files.