Package Details: vscodium-bin 1.126.04524-2

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Conflicts: vscodium
Provides: codium, vscode, vscodium
Submitter: ckatri
Maintainer: Icelk
Last Packager: Icelk
Votes: 395
Popularity: 8.08
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2026-08-26 12:02 (UTC)

Pinned Comments

<deleted-account> commented on 2021-05-12 00:31 (UTC)

@Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 31 Next › Last »

Kycko commented on 2025-12-10 14:46 (UTC)

Strangely this package doesn't provide Plasma 6 global menu while AUR package 'vscodium' does.

Icelk commented on 2025-11-26 21:25 (UTC)

@Nemris @tyrheimdal

Thanks for the suggestions! They should be implemented now.

tyrheimdal commented on 2025-11-24 16:33 (UTC)

Seconding what @nemris said, apart from the "Optional" part. Using rm on find with unknown output is DANGEROUS.

Additionally there's no reason to do manually chown and chmod on the SUID chrome-sandbox binary. Just use install -Dm4755 SRC DEST instead.

LICENSE handling is missing, see: https://wiki.archlinux.org/title/PKGBUILD#license

You don't have to specify ${srcdir} as you are already in the directory when using the package() function. It's generally a bad idea to switch directory in the function. See https://man.archlinux.org/man/PKGBUILD.5#PACKAGING_FUNCTIONS for more details.

If you are unsure, consider taking inspiration from other official chrome-based packages like: https://gitlab.archlinux.org/archlinux/packaging/packages/chromium/-/blob/main/PKGBUILD?ref_type=heads#L277-346

Nemris commented on 2025-11-23 19:43 (UTC)

Optionally, you can do away with both the cding and rm by having find do all the work:

diff --git a/PKGBUILD b/PKGBUILD
index 09f0e98..e12ae9c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -51,9 +51,7 @@ package() {
   install -d -m755 "${pkgdir}/usr/share/"{applications,pixmaps}
   cp -r "${srcdir}"/* "${pkgdir}/opt/${pkgname}"
   # remove source files links
-  cd "${pkgdir}/opt/${pkgname}"
-  rm $(find "${pkgdir}/opt/${pkgname}" -maxdepth 1 -type l)
-  cd -
+  find "${pkgdir}/opt/${pkgname}" -maxdepth 1 -type l -delete
   ln -s "/opt/${pkgname}/bin/codium" "${pkgdir}/usr/bin/codium"
   ln -s "/opt/${pkgname}/bin/codium" "${pkgdir}/usr/bin/vscodium"
   install -D -m644 "${srcdir}/vscodium-bin.desktop" "${pkgdir}/usr/share/applications/codium.desktop"

Icelk commented on 2025-11-22 18:16 (UTC)

@wackbyte

Thanks! That should be fixed now.

wackbyte commented on 2025-11-18 02:39 (UTC)

The PKGBUILD seems to install files that are symlinks into the build directory, which are easily broken, particularly when building in a clean chroot.

In /opt/vscodium-bin/ I have:

code.svg -> /startdir/code.svg
vscodium-bin.install -> /startdir/vscodium-bin.install
vscodium-bin.sh -> /startdir/vscodium-bin.sh
vscodium-bin-wayland.desktop -> /startdir/vscodium-bin-wayland.desktop

Icelk commented on 2025-11-10 16:08 (UTC)

@hiruocha

I didn't find a way to do it without using bash's eval which opens users up to shell injection vulnerabilities. If you find one please send a diff :)

Icelk commented on 2025-11-10 16:07 (UTC)

@terashy

Not from me at least. Do you have vscodium-bin-features installed? It seemed to cause problems. Otherwise, try with downloading the binary from the vscodium github and report back :)

willker commented on 2025-11-04 18:46 (UTC) (edited on 2025-11-04 18:57 (UTC) by willker)

Hi, could you modify the launch script so that lines in codium-flags.conf support shell variable expansion (like $HOME)? Currently, variables are passed literally and not expanded, which limits flexibility.

Thanks!（sorry for using AI translate）

terashy commented on 2025-11-04 11:13 (UTC) (edited on 2025-11-04 11:19 (UTC) by terashy)

Is there an official fix for Extensions not showing in Extensions? I experience the same issue now. The problem leads addition to not be able to add or remove Extensions.

Post from jongeduard: ` jongeduard kommentierte 2025-10-26 13:15 (CET) (geändert am 2025-10-26 13:19 (CET) von jongeduard) Something seems wrong with the latest update.

Extensions are broken. Nothing is shown and it keeps searching forever.

When I downgrade to a previous version, everything works again. `

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 31 Next › Last »