-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No permalink to latest VSCode distributable #1084
Comments
And would any of you be kind enough to review the python script and tell me if it is a feasible way to distribute the package. PS: I have tested it by hardcoding the Linux-x64 download link and it seems to go without a hitch on Ubuntu GNOME 15.10, Kali Linux 2.0 and Mint. |
@hashhar here are the static links that always point to the latest VS Code distribution. We are also going to add these links to download confirmation pages so people can restart their downloads if they don't automatically start (see #1019 ). osx: http://go.microsoft.com/fwlink/?LinkID=620882 |
Thanks a lot. I can now get back to finishing the installation scripts. |
The script is now live at https://github.com/hashhar/vscode-universal-installer |
I basically need a permalink to the latest VSCode distributable.
I was trying to write a Python installation script which will download the latest release, unzip it, make symlinks, copy a VSCode.desktop I have written (here as a fork of VSCode) into /usr/share/applications to register a launcher into Unity and GNOME.
I have stumbled upon an issue though. Since no releases are being done (not the source files, the actual installation zipballs which are downloaded from the website) I cannot use the GitHub Releases API (I wrote a preliminary proof of concept here).
I also wasn't able to trigger a click on the download page. (I can do it with Mechanize but that is a dependency and I want the script to be as self sustained as possible).
So how do I go about this? I basically need a permalink to the latest VSCode distributable.
The text was updated successfully, but these errors were encountered: