Arch Linux User Repository

if you are having an issue or getting an error you can

• email me: check pkgbuild for email
• dm me on discord: witheringaway

i should respond quickly

tested helpers

• helper name, last tested version - note
• works:
• pacman, officially supported
• pikaur, officially supported - main aur helper i use
• yay, 1-18 - hook is often double checked with
• paru, 1-16 - hook does not work with sudo paru, just dont use sudo when using paru
• bauh, 1-16
• octopi, 1-16
• slight jank:
• pamac, 1-16 - has horrible architecture, script must go on a scavenger hunt to find who initiated the transaction

Regarding vesktop, only if the full client api isn't needed. In most cases, I'd (personally) prefer vesktop. but it isn't 1:1 in some regards.

Whether this package is obsolete, not entirely: it still is useful for patching the initial install. I'm not 100% on the new update mechanism, and discord hasn't pushed an update through it yet (that i've witnessed).

I've set up inotifywait pointed at the symlink ~/.config/discord/Discord and a patch script to handle reapplying when it changes. Will have a stronger opinion once I've witnessed discords new behavior.

so this package is made obsolete? do people just need to use vesktop at this point?

Unfortunately I don't think a hook is the right trigger for this anymore.

since Discord 1.0.136's bootstrap rework, the app itself lives at ~/.config/discord/app-X.Y.Z/ and is updated by Discords own user-side updater.

pacman transactions no longer line up with the actual update events.

Probably still has a place for the initial install if reworked to invoke vencordinstallercli -location <user-side path>

thanks for the heads up Jonathing, ill see what i can do, if anything

FYI -- The new Discord bootstrap in 1.0.136 has broken Vencord Installer (and this hook by extension).

if you are having an issue or getting an error you can

• email me: check pkgbuild for email
• dm me on discord: witheringaway

i should respond quickly

tested helpers

• helper name, last tested version - note
• works:
• pacman, officially supported
• pikaur, officially supported - main aur helper i use
• yay, 1-18 - hook is often double checked with
• paru, 1-16 - hook does not work with sudo paru, just dont use sudo when using paru
• bauh, 1-16
• octopi, 1-16
• slight jank:
• pamac, 1-16 - has horrible architecture, script must go on a scavenger hunt to find who initiated the transaction

hmm thats weird give me a second to look into it, do you have a way i can communicate with you directly?

:c

HOOK  Installing Vencord for stable branch...
panic: VencordInstaller was run as root but neither SUDO_USER nor DOAS_USER are set. Please rerun me as a normal user, with sudo/doas, or manually set SUDO_USER to your username

goroutine 1 [running]:
main.init.0()
    /go/banana/Installer/find_discord_linux.go:50 +0x556
HOOK  An error occurred. If unresolvable, contact the package maintainer: https://aur.archlinux.org/packages/vencord-hook
Error: command failed to execute correctly

omg thank you so much! i've been STRUGGLING to get the vencord installer to run within a hook without throwing files in not so useful places ;w; this is defo a weight off my shoulders

Thanks d3adb5, just pushed.