Package Details: vscodium-bin 1.43.2-1

Git Clone URL: (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL:
Licenses: MIT
Conflicts: code
Provides: code
Submitter: plague-doctor
Maintainer: plague-doctor (oguzkagan, Rowisi)
Last Packager: Rowisi
Votes: 74
Popularity: 10.44
First Submitted: 2019-04-18 23:11
Last Updated: 2020-03-25 13:02

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

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.

arp12 commented on 2018-12-24 08:26

:: failed to verify integrity or prepare vscodium package

nix6839 commented on 2018-12-16 01:45

I think it's a good idea to add vscodium-url-handler.desktop file. (Ref to

plague-doctor commented on 2018-11-23 23:06

Then the differences are: it is a different project and it is up to date ;-)

FabioLolix commented on 2018-11-22 19:59

code in community is binary and don't have MS branding/telemetry/licensing, which are instead in visual-studio-code-bin

plague-doctor commented on 2018-11-22 19:56

A difference, as per project page: "Free/Libre Open Source Software Binaries of VSCode without MS branding/telemetry/licensing".

FabioLolix commented on 2018-11-22 16:28