Package Details: visual-studio-code-insiders 1593414285-1

Git Clone URL: https://aur.archlinux.org/visual-studio-code-insiders.git (read-only, click to copy)
Package Base: visual-studio-code-insiders
Description: Editor for building and debugging modern web and cloud applications (insiders version)
Upstream URL: https://code.visualstudio.com/
Keywords: vscode
Licenses: custom: commercial
Submitter: dcelasun
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 29
Popularity: 1.44
First Submitted: 2016-11-22 07:44
Last Updated: 2020-06-29 08:12

Pinned Comments

dcelasun commented on 2016-11-22 07:48

IMPORTANT: This package always installs the latest insider build (see pkgver() function), so if you want daily updates, just run "makepkg -si" everyday and it will update. I won't be updating pkgver every single day.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

dcelasun commented on 2020-06-29 08:13

@sjq fixed, thanks!

sjq commented on 2020-06-29 01:18

This package will first download the old version of vscode file, then update the pkgvar!! See the link below for more detail.@fpigeonjr @dcelasun @dufferZafar

https://www.archlinux.org/pacman/PKGBUILD.5.html

To solve this, try to use $(pkgvar) instead of ${pkgvar} in the source, this will make it always call pkgvar() and go to download the latest version of the package. @dcelasun

fpigeonjr commented on 2020-06-11 18:29

thanks @dcelasun! That worked for me. Thanks for your guidance.

dcelasun commented on 2020-06-10 13:40

@fpigeonjr I'm not familiar with yay but I imagine it's having trouble with the pkgver() function. Try downloading the tarball and installing manually with makepkg -si.

fpigeonjr commented on 2020-06-10 13:36

I installed this package using :

yay -S visual-studio-code-insiders

and is working fine but the program tells me I need to update.

When I run yay -Syu it doesn't update?

How do I update this package?

esrevinu commented on 2020-05-30 09:32

I have the same issue as described by @dufferZafar. This PKGBUILD seems to fix it: https://gitlab.com/snippets/1981800

dufferZafar commented on 2020-05-14 08:23

This package doesn't seem to be updating for me.

I run yay -S visual-studio-code-insiders and it goes on to download and install code_x64_1587622013.tar.gz which is an older version of VS Code Insiders (uploaded on Thursday 23 April 2020 11:36:53 AM IST) and the one that is specified by default in the pkgver line

But when I run the pkgver() line: IFS='/' read -ra ADDR <<< $(curl -ILs -o /dev/null -w %{url_effective} https://vscode-update.azurewebsites.net/latest/linux-x64/insider); echo "${ADDR[5]}" | sed 's/code-insider-//g' | sed 's/.tar.gz//g' | sed 's/-/./g'

I get 1589394433 which is the latest version (Wednesday 13 May 2020 11:57:13 PM IST) and the one that I expected to install.

I'm not sure what's broken, this package, or my system somehow.

For now, I've cloned this repo and edited the PKGBUILD to manually change the pkgver to 1589394433.

dcelasun commented on 2020-04-24 06:44

@Nowaker:

Keywords exist on PKGBUILD files but AUR doesn't expose it in RPC API

I'm not talking about the PKGBUILD, I've added the keyword to from the AUR UI, see here. Is that not accessible via API?

Looks like a gray area, maybe not worth any further thinking

Thanks for investigating, I'll definitely keep it in mind and will submit a request myself if it ever becomes an issue.

From a pragmatic point of view, the best course of action is to delete provides=code from here as its presence provides no benefits while being detrimental to the experience

That's fair, I'll remove it.

Nowaker commented on 2020-04-23 22:26

Thanks for your answer!

I just added it as a keyword. If your AUR helper doesn't check those, please file an issue with them.

No AUR helpers will ever use keywords for AUR searches. Keywords exist on PKGBUILD files but AUR doesn't expose it in RPC API. The only way for AUR helpers to search by keyword is to clone all AUR packages and search on disk. So obviously that's not a feasible solution at all. :) See: https://wiki.archlinux.org/index.php/Aurweb_RPC_interface. Adding vscode to the description is currently the best way of "announcing" the existence of this package to the world.

This seems like a cosmetic change

I've seen several packages deleted because of non-conformity to the naming guideline: https://wiki.archlinux.org/index.php/Nonfree_applications_package_guidelines#Package_naming I'm the last person to do "Submit Request" -> "Deletion", but there are many purists on AUR that may try that. Some people may try a sneaky approach of hijacking the package by creating visual-studio-code-insiders-bin themselves, and them doing "Submit Request" -> "Merge", "Merge into: visual-studio-code-insiders-bin", and it will fly... Unfortunately.

EDIT: On a second thought, the linked guideline applies to "non-free" software. Whether VS Code Insiders is free or non-free is pretty debatable... Looks like a gray area, maybe not worth any further thinking.

I'm not sure if the package actually conflicts with the one from the community repo, but I'll check.

Oh, that makes sense. While technically correct and in line with the guidelines in https://wiki.archlinux.org/index.php/PKGBUILD#provides, the end result is your VS Code and VS Code Insiders packages can't be installed side by side even though they don't have any conflicting files. :( From a pragmatic point of view, the best course of action is to delete provides=code from here as its presence provides no benefits while being detrimental to the experience. This is still a case:

:: visual-studio-code-insiders and visual-studio-code-bin are in conflict (code). Remove visual-studio-code-bin? [y/N] 

Thanks for all your work! I really appreciate it.

dcelasun commented on 2020-04-17 08:23

Can you add vscode somewhere to the description, to make it easy to find with AUR helpers?

I just added it as a keyword. If your AUR helper doesn't check those, please file an issue with them.

consider renaming this to visual-studio-code-insiders-bin

This seems like a cosmetic change especially since upstream doesn't provide source-only distributions of Visual Studio Code (the open source project is called "code")

it still seems to conflict with other VSCodes [...] Most likely because of provides=('code')

No, because visual-studio-code-bin has conflicts=(code). I'm not sure if the package actually conflicts with the one from the community repo, but I'll check.