| 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: | 1418 |
| Popularity: | 19.68 |
| First Submitted: | 2017-12-18 19:14 (UTC) |
| Last Updated: | 2024-05-03 05:35 (UTC) |
version 1.29.1 uses/installs flatmap-stream 0.1.1 for the references-view extension.
If you have installed this package, you should read over https://github.com/dominictarr/event-stream/issues/116#issue-382854428 and determine if you are affected or not.
All right, thanks for voicing your opinions everyone. I've decided to remove pylint as an optdepend in the next version. I also won't be adding any language specific dependencies from now on.
IMO, pylint is an optional dependency for an extension you can install, not for the editor itself, so it probably shouldn't be an optdepend. Optional dependencies for things like trash support definitely make sense because it's an optional editor feature, but I can think of a number of other extensions that also ask for things to be installed (the Go extension prompts to install linters, C/C++ extension asks about clang-format, etc), and I wouldn't personally want those added as optdepends either. If you configure the extension to specify a different linter (flake8/pep8), then it'll show the same prompt but for that other tool too, pylint's just the default. Always running pylint is going to stop being the default in the python extension anyway [1] [2].
[1] https://github.com/Microsoft/vscode-python/issues/974
[2] https://github.com/Microsoft/vscode-python/issues/3007
(Disclaimer, I work on the python team at Microsoft, but this isn't any sort of official opinion or anything. I just noticed the added dep during an update on my personal machine.)
And of course all of this is just my opinion, so feel free to change my mind, if you know something I don't. :)
*But only packages, that can be used by that package without any plugins. (= If visual studio code does not support python without additional plugin, python-pylint should not be added as optdependcy, but if visual studio code support python by default and opening python file shows that warning without installing additional plugin, we should add python-pylint as optdependcy.)
@elgs I think, that optdepends are not about what you want, but about what you may want. So they should contain packages, that can be for someone only "pollution".
Personally, I think, that in optdepends should be every package, which can be used by that package in any way. Also sometimes it is good idea to add as optdependcy package, that is not used by that package, but can make usage of that package significantly easier. (There are lot of examples of that in official Arch Linux packages.)
Personally, I don't mind if there is a ton of optdepends.
I know you don't mind. But other people may see it as pollution. Many people don't like anything which is not necessary for them.
Fair point. You can't just add a ton of optdepends for every eventuality; you need to draw a line somewhere.
I see two main criteria, each of which is a good reason for an optdepends:
The package is essential for a basic core functionality ( here 'basic Python support'. VSC complains about this package missing, not about 'pyflakes' )
The package is arguably supposed to be installed --asdeps. If there is no package to optdepend on it, then it becomes an orphan as far as Pacman is concerned.
Both rules apply here imo. You could even make a point for XDebug for PHP even though VSC doesn't complain about that one. QtCreator for example has even git, mercury, valgrind etc. as optdepends.
If it gets too much, as it might happen with multi-language editors, then that's rather an argument for splitting the package into multiple optimized ones, like with Eclipse and Netbeans, not for letting the user whack-an-error-message.
Personally, I don't mind if there is a ton of optdepends. Let me know on install what else might be useful in combination with the main package.
I also think adding python specific things as dependency (even optional) is a bad idea.
@Caldazar that's a really bad idea.. VSCode has nothing with Python. So let's add Java, dotnet, and all other languages as a optional dependency -.- That's also does not change anything, so I wonder why that should be a optional dependency. There is also other python linter: pyflakes.
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.