Arch Linux User Repository

Yeah, that sounds like a sound idea. Also, take a look at my changes and perhaps adopt most of them.

Is it the desired behaviour that the noisetorch binary sets the capabilities for itself? As noisetorch is no longer usable without the capability cap_sys_resource I would assume that the best place to set it is the install file (like it is done for e.g. ping).

Ideally I'd want to separately package the C dependencies and dynamically link them in. As a start, I packaged rnnoise. Can you try linking that dynamically instead of the weird soname embedding that's going on?

Apart from that, this would be my current PKGBUILD: https://gitlab.archlinux.org/-/snippets/5

I did some minor cleanup on the PKGBUILD. It follows the go packaging guidelines as far as I can tell, and I believe it is reproducible. Updating the pkgver in the PKGBUILD is all I have been doing for the past couple releases, otherwise the current version builds no problem without intervention.

Make sure to clean up the package and make it reproducible/make it comply with go package guidelines.

@Svenstaro Absolutely not, go right ahead! Is there anything you need me to do?

@znoble360 The readme is indeed incorrect, but if the application prompts for creds to set the capability, it appears to operates on itself instead of a fixed path 1 and 2.

That executable function might have problems dealing with symlinks, but if the package is installed as-is, it should work. I haven't touched the setcap command on my system and I see:

$ getcap /usr/bin/noisetorch
/usr/bin/noisetorch cap_sys_resource=eip

You mind me pulling this into [community]?

After a bit of futzing around, I figured out why the CAP_SYS_RESOURCE authorization was failing for me. It looks like since you install noisetorch in /bin instead of home and the original attempts to authorize noisetorch in the user home, the user can't use the autofix for CAP_SYS_RESOURCE. The official command in the git sudo setcap 'CAP_SYS_RESOURCE=+ep' ~/.local/bin/noisetorch also doesnt work for the same reason, so one must instead replace ~/.local/bin/noisetorch with the new location of the binary.

for the package conflicts, should the -bin -git variants still conflict with this one? so basically this package conflicts with nothing, while the other -git -bin variants contain all the conflicts?

Hello, thanks for this package! Version 0.9.0 is went out three days ago :)