Package Details: vscodium-bin 1.38.1-1

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Provides: code
Submitter: plague-doctor
Maintainer: plague-doctor
Last Packager: plague-doctor
Votes: 42
Popularity: 8.886607
First Submitted: 2019-04-18 23:11
Last Updated: 2019-09-12 22:19

Latest Comments

1 2 Next › Last »

GAZ082 commented on 2019-08-11 19:41

==> Validating source files with sha256sums... vscodium-bin.desktop ... Passed vscodium-bin-1.37.0-1.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

joseluisq commented on 2019-08-10 20:05

VSCodium user here, Dear AUR maintainer, please try to keep this package in sync with releases upstream. Since there is a big delay between the new releases of vscodium and this package.

galvez_65 commented on 2019-06-16 21:48

AUR shows the package as rel 2 but PKGBUILD states rel 1.

Anonymous comment on 2019-06-16 17:24

Hello,

The pkgrel in .SRCINFO is different from the one in PKGBUILD. It should be 1, not 2.

Anonymous comment on 2019-06-11 03:54

Hello,

Version 1.35.0 of VSCodium has introduced some breaking changes that are not accommodated in this release. The binary has been renamed to "codium", so "vscodium-bin.desktop" and the symlinks created in the PKGBUILD must be updated to use the new binary.

More info: https://github.com/VSCodium/vscodium/pull/176

madddi commented on 2019-05-04 15:38

Hi,

the hash in PKGBUILD differs from the one in the GitHub release (https://github.com/VSCodium/vscodium/releases/tag/1.33.1). The integrity check fails. This patch...

diff --git a/PKGBUILD b/PKGBUILD
index af799b7..0d90658 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -22,7 +22,7 @@ source=(
        )
 noextract=("${pkgname}-${pkgver}-${pkgrel}.tar.gz")
 sha256sums=('44c07450999d260672edfd34215fde0ca11829a38f89592f4d1f035e1dd5012a'
-            'ff90d3541627e380afc7026c0ec9b451510a9440e457c951c8a3e3261aefb017')
+            '7a87f19bc48cbe017321c72da244d879a7da364b92b3a89b742d437ffcd585d3')

Fixes it.

tsouhaieb commented on 2019-04-17 07:29

why it conflict with visual-studio-code-bin, if it's about code cli command, under osx, it's renamed vscodium for vscodium, and visual studio code and vscodium, can run together without conflicting between each other, also because each one of them use a different folder of the extensions. (visual studio code $HOME/.vscode and vscodium i think $HOME/.vscode-oss.

after testing, also under linux, code is replaced with vscodium, the extensions are installed under .vscode-oss,

by replacing provides=('code') by provides=('vscodium') , they can be installed beside each other without problem, i already tested

joseluisq commented on 2019-04-12 21:13

I vote too for a vscodium-bin package.

ShayBox commented on 2019-04-12 12:36

The package name should be vscodium-bin, this should be compiling tagged github releases.
(I would suggest changing this to compile from tagged releases and moving this PKGBUILD to vscodium-bin)

It also does not need to have conflicts with visual-studio-code-bin as it uses entirely separate config directories from them, it can be installed side by side like code

Actually I take that back, it conflicts with code because it's using the .vscode-oss folder in $HOME for its extensions

OriginCode commented on 2019-01-11 08:55

The package name should be vscodium-bin.