OK thanks, we'll skip 1.7 for now.
Search Criteria
Package Details: visual-studio-code-bin 1.89.1-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/visual-studio-code-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | visual-studio-code-bin |
| Description: | Visual Studio Code (vscode): Editor for building and debugging modern web and cloud applications (official binary version) |
| Upstream URL: | https://code.visualstudio.com/ |
| Licenses: | custom: commercial |
| Conflicts: | code |
| Provides: | code, vscode |
| Submitter: | dcelasun |
| Maintainer: | dcelasun |
| Last Packager: | dcelasun |
| Votes: | 1423 |
| Popularity: | 20.11 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-05-12 05:01 (UTC) |
Dependencies (17)
- alsa-lib
- gcc-libs (gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR)
- gnupg (gnupg-gitAUR, gnupg-largekeysAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR, gtk3-classic-xfceAUR)
- libnotify (libnotify-gitAUR)
- libsecret
- libxkbfile
- libxss
- lsof (lsof-gitAUR)
- nss (nss-hgAUR)
- shared-mime-info
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-betterlockscreenAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR) (optional) – Needed for move to trash functionality
- icu69AUR (icu69-binAUR) (optional) – Needed for live share
- libdbusmenu-glib (optional) – Needed for KDE global menu
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, bitw-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – Needed for settings sync
Required by (17)
- azure-sphere-sdk (requires code) (optional)
- code-appicons (requires code)
- code-features (requires code)
- code-features-insiders (requires code)
- code-icons (requires code)
- code-marketplace (requires code)
- code-nautilus-git (requires code) (optional)
- dokytree (requires code) (optional)
- dokytree-git (requires code) (optional)
- meta-package-manager (requires code) (optional)
- nautilus-code (requires code) (optional)
- neopo-git (optional)
- nwscript-code (requires code)
- rust-analyzer-vscode-git (requires code)
- stm32pio (requires code) (optional)
- unity-editor-lts (optional)
- unreal-engine-bin (requires code) (optional)
Sources (7)
dcelasun commented on 2016-11-03 07:14 (UTC)
elgaton commented on 2016-11-03 07:12 (UTC)
To the maintainer: even though this package was correctly flagged out of date, please do not update it - the new release (1.7) was rolled back because it overloaded the npmjs.org service: https://code.visualstudio.com/updates#_17-rollback
epse commented on 2016-10-24 18:21 (UTC)
It no longer provides vscode or visualstudiocode, it is code now. Should update package description.
dcelasun commented on 2016-10-11 16:46 (UTC)
@ederjc: You're right, libxss should be a dependency. I've released 1.6.0-2 to fix it.
ederjc commented on 2016-10-11 16:40 (UTC) (edited on 2016-10-11 16:42 (UTC) by ederjc)
I had trouble uninstalling the previous version and install the current, the vscode simply not executed. installed with pacman atom and to my surprise vscode he returned to start. removing the atom and dependencies it stopped working. My solution was to check each dependency of the atom and installing dependence "libxss" the VSCode starts normally. Why got this bug?
keysona commented on 2016-10-11 06:49 (UTC)
Oh, my god.
The editor is grow better and better.
The inclued terminal is greate, they have fixed the terminal output.:)
Atom is greate, but slow?
ST also greate, but hard to use?
For me, I chooes visual code.
dcelasun commented on 2016-10-10 21:06 (UTC)
Updated to 1.6.0. For the -bin prefix issue, I've updated the package description as a middle ground between renaming the package and doing nothing.
dcelasun commented on 2016-10-10 07:00 (UTC)
Renaming an AUR package would prevent all the AUR helpers from updating it ("replaces" only works for pacman w/ repositories).
Considering the popularity of the package (and hence the number of people potentially effected), I don't think renaming is a good idea, especially for cosmetic purposes.
jugs commented on 2016-10-09 22:38 (UTC)
Definitely need to rename this package to -bin as has been mentioned several times. Current name is misleading.
markand commented on 2016-10-06 09:14 (UTC)
Renaming a repository to match the guidelines is not a problem. Please add a -bin suffix.
Pinned Comments
dcelasun commented on 2017-11-15 06:20 (UTC) (edited on 2020-02-06 21:33 (UTC) by dcelasun)
FREQUENTLY ASKED QUESTIONS (read before flagging or commenting!)
This is the official binary distribution from Microsoft. The one in the community repo is an unofficial build made from source. Beyond the license difference and branding, there are some proprietary features not available in the open source version.
Please check this page before flagging as out-of-date. If there is no new version on that page, it's not yet released. A tag on Github is NOT a release! If you can see the new version on the updates page but the AUR package is still not updated, flag it and give it time. It's usually done within a day or two.
Sometimes AUR helpers do weird things. Download the tarball and install it manually with
makepkg -si. If that works, report the problem to your AUR helper's upstream, not here.xdg-openuses vscode, not my file manager! How do I fix this?Install shared-mime-info-gnome. Also see this reddit thread.
Just because $X is not required to open the app, doesn't mean there is nothing that depends on it. Always search the comment history on AUR to see if that dependency has been previously discussed before writing your own comment. Still nothing? Then use namcap to make sure it's really not needed. If namcap doesn't complain, please leave a comment here and I'll investigate.
The problem might be a packaging issue (wrong paths, dependencies, icons), so please write a comment here first. If you don't get a reply, or if someone says it's an upstream issue, you can report it on Github.
No, you won't get a reply. Please stop doing this. Leave a comment here instead and be patient.