Package Details: apulse-git 0.1.12_r5_gbcd55c8-1

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

Latest Comments

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. https://lists.archlinux.org/pipermail/aur-general/2017-March/033246.html

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.

SanskritFritz commented on 2017-03-08 15:04 (UTC)

That is true if the PKGBUILD never changes. But what if the build process or whatever changes? I have to download the new package. Epoch change is just perfect to sign such changes.

WorMzy commented on 2017-03-08 14:56 (UTC)

I don't bump epochs for -git packages as a rule. If you are using a -git package, you should be rebuilding it frequently and not relying on AUR helpers to alert you to new versions.

SanskritFritz commented on 2017-03-08 14:22 (UTC)

If you make that change, please increase the epoch number, so that automatic tools would recognise the version change.

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

So it is just the "r". I'll add it shortly. Note that it'll be seen as a downgrade since 0.1.7_13_gf445ae7 > 0.1.7_r13_gf445ae7 in vercmp.

Ralf_Mardorf commented on 2017-03-08 12:45 (UTC) (edited on 2017-03-08 12:48 (UTC) by Ralf_Mardorf)

As pointed out by the package guidelines, if possible the format should be 1.2.r3.gabcdef7 and fortunately it is possible.

WorMzy commented on 2017-03-08 11:22 (UTC)

You'll need to be more specific about how the current PKGBUILD is "broken". Do you just want an "r" before the revision number, or do you object to underslashes (which, by the way, are treated the same as periods)?

Ralf_Mardorf commented on 2017-03-07 22:36 (UTC) (edited on 2017-03-07 22:41 (UTC) by Ralf_Mardorf)

Please fix the PKGBUILD by following https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

Lone_Wolf commented on 2017-03-07 21:03 (UTC)

Works great with firefox-52.0-1 (the one without alsa support) .

WorMzy commented on 2015-02-06 15:27 (UTC)

I've switched to 'git describe --tags' for the pkgver, please note that this will appear as a downgrade when you install it.

WorMzy commented on 2014-10-17 20:28 (UTC)

If you found a bug in the latest git source, please report it upstream, or it'll probably come back to haunt you when it gets tagged as stable.

quellen commented on 2014-10-17 19:35 (UTC)

this version is bad, the microphone of my USB webcam didn't worked on skype (even though I had edited ~/.asoundrc) Use this version, is better: https://aur.archlinux.org/packages/apulse/ and if you use a webcam usb, edit your "~/.asound" like this: https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#Setting_the_default_microphone.2Fcapture_device