Package Details: visual-studio-code-oss 1.13.1-1

Git Clone URL: https://aur.archlinux.org/visual-studio-code-oss.git (read-only)
Package Base: visual-studio-code-oss
Description: Visual Studio Code for Linux, Open Source version
Upstream URL: https://code.visualstudio.com/
Keywords: IDE Microsoft vscode
Licenses: MIT
Conflicts: vscode-oss
Provides: vscode-oss
Submitter: Zrax
Maintainer: Zrax
Last Packager: Zrax
Votes: 57
Popularity: 8.793757
First Submitted: 2015-12-02 18:11
Last Updated: 2017-06-16 16:25

Pinned Comments

Zrax commented on 2017-05-07 17:19

NOTE: To enable the non-free features of this package (including the Extension Gallery, release notes, etc), either modify the PKGBUILD to set VSCODE_NONFREE=1, or set it on the build command line:
$ makepkg -siC VSCODE_NONFREE=1

Latest Comments

Zrax commented on 2017-05-07 17:19

NOTE: To enable the non-free features of this package (including the Extension Gallery, release notes, etc), either modify the PKGBUILD to set VSCODE_NONFREE=1, or set it on the build command line:
$ makepkg -siC VSCODE_NONFREE=1

ItachiSan commented on 2017-05-07 09:50

@Zrax, is it intended that the extensions store is disabled?
As I noticed just now that all my extensions are pretty outdated...
If yes, should I download them manually? Or is there a switch to re-enable the extensions store?
--- EDIT
Just looked at sources, I do feel dumb. lol
Got too much used to pacaur :P
--- EDIT 2
I think it would be nice to add a top comment here saying to people that they can enable extensions store by using the environment variable or tweaking the PKGBUILD

opotonil commented on 2017-05-05 19:14

@hutliver
Built without troubles in a clean environment, you can see the build here:
https://travis-ci.org/localnet/aurci/builds/229240678

And, if you want, you can download the built package (non free) from here:
https://github.com/localnet/aurci/releases

hutliver commented on 2017-05-05 18:40

cannot build this package, get the following error:

> oniguruma@6.1.1 install /tmp/yaourt-tmp-wtiger/aur-visual-studio-code-oss/src/vscode/node_modules/oniguruma
> node-gyp rebuild

make: Entering directory '/tmp/yaourt-tmp-wtiger/aur-visual-studio-code-oss/src/vscode/node_modules/oniguruma/build'
CC(target) Release/obj.target/oniguruma/deps/onig/regcomp.o
make: cc: Command not found
make: *** [oniguruma.target.mk:140: Release/obj.target/oniguruma/deps/onig/regcomp.o] Error 127
make: Leaving directory '/tmp/yaourt-tmp-wtiger/aur-visual-studio-code-oss/src/vscode/node_modules/oniguruma/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:194:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.10.13-1-ARCH
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /tmp/yaourt-tmp-wtiger/aur-visual-studio-code-oss/src/vscode/node_modules/oniguruma
gyp ERR! node -v v7.10.0
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok

Also, can anyone list out the differences between this and the 'visual-studio-code' package?

opotonil commented on 2017-05-05 18:25

@Fafa123
1. Just because you build the binary yourself does not make it a different package. It literally is the exact same package if you keep the product_json.patch (at least that is what Microsoft is saying and why should they lie it is obvious that the extension gallery is the telemetry source).

- After install the latest version of this package, without apply product_json.patch, I having continue disabling the telemetry in the configuration:
"telemetry.enableTelemetry": false
"telemetry.enableCrashReporter": false

2. The patch is optional yes. Though it is illogical to call this package oss if you enable the patch by default.

- Why? Does applying the patch make the package copyrighted? Those values can be getted, for example, with wireshark doing reverse engineer as does other OSS packages as Nouveau. right?

3. What is stopping you from doing it the other way around? Disable the patch and inform the user to enable it (which enables telemetry and the extension gallery). Then keeping the name OSS is perfectly valid. Currently this is not unfortunate. This is just terribly misleading. I don't want to blame you or anything, neither is this Debian repo I get that. But we all should strive for clear and obvious namings especially in such a simple case. There is no reason at all to keep the product_json.patch be applied by default just because some idiots don't understand what OSS means.

- I don't understand it, after see the default configuration the telemetry is enabled on both cases. Can be because I don't know much about laws and copyright, or can be my low english level, or simply I'm a idiot... can be. But I don't understand.

Marcel_K commented on 2017-05-05 16:17

I only get a blank (dark gray) window with (smaller) menu items since version 1.12.0. Renaming ~/.vscode-oss and ~/.config/Code - OSS didn't solve it. Anyone else having this issue?

Zrax commented on 2017-04-29 22:02

Sorry, should be fixed now.

opotonil commented on 2017-04-29 21:48

Can you update sha256sum of visual-studio-code-oss.desktop (https://travis-ci.org/localnet/aurci/builds/227025827):

==> Validating source files with sha256sums...
vscode ... Skipped
startup_script.patch ... Passed
visual-studio-code-oss.desktop ... FAILED
==> ERROR: One or more files did not pass the validity check!

Zrax commented on 2017-04-28 22:15

Patching product.json does not make it "literally the exact same package". Even the patched product.json is not identical to the version in the binary download, regardless of the state of the rest of the files. It does enable the use of the telemetry and the extension gallery, which are otherwise features only available in the proprietary version, but enabling features doesn't make it identical. Whatever, the point is probably splitting hairs anyway.

Your point about enabling the proprietary features in a package (misleadingly) named "-oss" is valid however. Since I never had a strong opinion about whether it's on or off by default anyway, I've disabled it by default.

Fafa123 commented on 2017-04-27 21:54

@Zrax
1. Just because you build the binary yourself does not make it a different package. It literally is the exact same package if you keep the product_json.patch (at least that is what Microsoft is saying and why should they lie it is obvious that the extension gallery is the telemetry source).

2. The patch is optional yes. Though it is illogical to call this package oss if you enable the patch by default.

3. What is stopping you from doing it the other way around? Disable the patch and inform the user to enable it (which enables telemetry and the extension gallery). Then keeping the name OSS is perfectly valid. Currently this is not unfortunate. This is just terribly misleading. I don't want to blame you or anything, neither is this Debian repo I get that. But we all should strive for clear and obvious namings especially in such a simple case. There is no reason at all to keep the product_json.patch be applied by default just because some idiots don't understand what OSS means.

As for the name in the AUR: The package you build from this (if OSS) is not called visual-studio-code anyway (refer to the product_json.patch). The OSS version is called "Code" not "Visual Studio Code". What you are doing here is mixing up the OSS "Code" with the propertiary "Visual Studio Code". According to your explanation BOTH visual-studio-code* AND *code-oss are invalid names for this package.

All comments