Arch Linux User Repository

As of 2024-09-16, this package is being co-maintained by official vesktop developers, and any packaging decisions they make will not be questioned on my part unless it's something harmful for the users, which is very unlikely to happen. As I see it coming, they will not use the system's electron on this package purposely, if you don't like it, use vesktop-electron, which is also maintained by the same devs.

Thanks!

Yeah, can you leave it as it was please? I'm running vesktop as it was before you started changing the PKGBUILD, and I have everything working: locales, vc, etc. Every single feature works as intended with no breakages.

All of those files are embedded into the app.asar file, which are being duplicated when installed this way. When I run pacman -U on your package, the installation size goes from 25.82MB to 261.99MB.

You can still leave it with supporting only the latest electron, but please at least change it back to use the system electron. If needed, re-add me as a co-maintainer and I'll keep taking care of those aspects.

Since 1.5.0-10, when Electron was removed from the dependencies, Vesktop now throws "/usr/bin/vesktop: line 11: exec: electron: not found" and won't start anymore, because the startup script still uses the system electron to start Vesktop.

Well, after checking, if we do not copy the whole thing to /usr/lib we don't get:

• locales
• some required libraries that are built-in
• some soname libraries
• more

The list of files generated actually are https://paste.rs/2uml1.txt

The right thing here is to just let it build as it's actually, remove electron from the dependencies and that's it. Even if we do something like discord_arch_electron, we need to add a fixed electron version for the package. Dropping the electron dependency for now.

@picokan packages are meant to build in a clean chroot environment (which was not happening because a clean chroot environment doesn't have any electron right there, and it will fail if the user didn't had any electron version installed on the machine too), not the user-specific environment, so we need to add a defined electron version in there, which is the system's electron. If you need, you can just update your PKGBUILD locally and add electron27 to the dependencies.

I will check the binary that's being copied.

Also, why is the whole resources folder getting copied to /usr/lib? Installing there all of the unneeded files from compiling vesktop, including a 177MB binary that has electron embedded, defeats the point of using a system electron in the first place.

@Edu4rdSHL The way I had it before was so you could install vesktop using any electron version you had on your system. Just using /usr/lib/electron is cleaner sure, but I just tried and couldn't install this package with electron27.

@EinfxchFinn, lets the user manage that. Now, you can add the flags to ~/.config/vesktop-flags.conf and they will be readed from there.

I just modified the PKGBUILD to always pick the latest electron using the convenient symlink from /usr/lib/electron, and, also dinamically putting the line before the "linux" occurrence so that we don't have to change the line number everytime.

Could you add --ozone-platform-hint=auto to the Exec variable in the .desktop file so that vesktop runs natively on wayland and not through xwayland? See: https://github.com/Vencord/Vesktop/issues/342

    #grabbin path for an installed electron
    #any ideas for a better way of doing this are welcome

Add electron to depends. Then it will be at /usr/lib/electron. Check /usr/lib/electron/version for the version number.