Search Criteria
Package Details: pulsecontrol-git 0.9-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/pulsecontrol-git.git (read-only, click to copy) |
---|---|
Package Base: | pulsecontrol-git |
Description: | A fork of pavucontrol aiming at better UX |
Upstream URL: | https://gitlab.freedesktop.org/oxayotl/pavucontrol/-/tree/fork |
Licenses: | GPL |
Submitter: | OxayotlTheGreat |
Maintainer: | OxayotlTheGreat |
Last Packager: | OxayotlTheGreat |
Votes: | 1 |
Popularity: | 0.013927 |
First Submitted: | 2024-05-23 21:35 (UTC) |
Last Updated: | 2024-05-25 09:43 (UTC) |
Dependencies (8)
- gtkmm-4.0
- json-glib (json-glib-gitAUR)
- libadwaita (libadwaita-gitAUR, libadwaita-without-adwaita-gitAUR)
- libcanberra
- git (git-gitAUR, git-glAUR) (make)
- meson (meson-gitAUR) (make)
- tidy (tidy-html5-gitAUR) (check)
- pulseaudio (pulseaudio-dummyAUR, pulseaudio-gitAUR) (optional) – Audio backend
Latest Comments
OxayotlTheGreat commented on 2024-05-25 09:44 (UTC)
Thanks!! I did that, noticed that it meant using pavucontrol's version tag, so I had a version tag of my own on pulsecontrol's git to be in 0.9 and not on 5.0.
yochananmarqos commented on 2024-05-24 16:51 (UTC)
@OxayotlTheGreat: Do not remove anything from the PKGBUILD and never edit .SRCINFO`manually.
Run
makepkg -od
and you'll see the pkgver() function generates the pkgver as I mentioned. Then runmakepkg --printsrcinfo > .SRCINFO
before committing and pushing.OxayotlTheGreat commented on 2024-05-24 16:41 (UTC)
Thanks!! Just to make sure I do think correctly, I should remove the
pkgrel=1
from PKGBUILD, and
from .SRCINFO, is that right? Nothing more, nothing less to do?
yochananmarqos commented on 2024-05-24 16:20 (UTC) (edited on 2024-05-24 16:20 (UTC) by yochananmarqos)
@OxayotlTheGreat: Ah, I didn't realize they're different.
By the way, I meant to address the pkgver itself, the pkgver() function is actually alright. You're inventing a pkgver instead of generating it with the pkgver() function which is 5.0+r155+ga7a7f55-1.
OxayotlTheGreat commented on 2024-05-24 15:46 (UTC) (edited on 2024-05-24 15:48 (UTC) by OxayotlTheGreat)
Thank you for your feedback, yochananmarqos! I pushed an update without the epoch and the unneeded dependency.
I wrote both the patch to port pavucontrol to Gtk4 and the pulsecontrol fork afterward. The fork is directly built upon the port, but looks and behave differently.
Here are screenshots of the same page in Gtk4 pavucontrol and in pulsecontrol, so you can compare:
Pavucontrol https://img.linuxfr.org/img/68747470733a2f2f692e696d6775722e636f6d2f777568654444682e706e67/wuheDDh.png
PulseControl https://img.linuxfr.org/img/68747470733a2f2f692e696d6775722e636f6d2f595a34374c38432e706e67/YZ47L8C.png
I cannot read the future, but I plan on working hard to make PulseControl a success, so this shouldn't be a pointless package.
yochananmarqos commented on 2024-05-24 14:39 (UTC)
pavucontrol
1.6.0 was updated to Gtkmm 4, so this fork will probably never be updated. This package is basically pointless now.yochananmarqos commented on 2024-05-23 23:58 (UTC)
By the way, this depends on
libsigc++-3.0
, notlibsigc++
. 3.0 is already pulled in as a dependency ofgtkmm-4.0
, so you might not have noticed.yochananmarqos commented on 2024-05-23 23:00 (UTC)
Please remove the epoch, they should almost never be used--especially for the first commit. Please also use a proper pkgver array according to VCS package guidelines.