Skip to content
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

Add Linux manual repo installation instructions #850

Closed
Tyriar opened this issue Feb 19, 2017 · 10 comments
Closed

Add Linux manual repo installation instructions #850

Tyriar opened this issue Feb 19, 2017 · 10 comments
Assignees

Comments

@Tyriar
Copy link
Member

Tyriar commented Feb 19, 2017

Follow up from microsoft/vscode#2973 microsoft/vscode#229

Isn't strictly needed for apt (as it's auto installed with the package) but probably a good idea to make it easier for people who want to automate their setup.

@Tyriar
Copy link
Member Author

Tyriar commented Feb 21, 2017

@gregvanl @waderyan with this, we want to change the default way that red hat users install VS Code to install via a script now, not the package. We'll probably need to rework this:

image

@Tyriar
Copy link
Member Author

Tyriar commented Feb 21, 2017

The new install is this when using the yum package manager:

# Install key
wget -O- -q https://packages.microsoft.com/keys/microsoft.asc > microsoft.asc
sudo rpm --import microsoft.asc
# Install repo
​​sudo sh -c 'echo -e "[code]\nname=Visual Studio Code\nbaseurl=https://packages.microsoft.com/yumrepos/vscode\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" > /etc/yum.repos.d/vscode.repo'
# Update yum's cache
yum check-update
# Install
sudo yum install code

Note that there are a bunch of other package managers that we will also want to include here.

@waderyan
Copy link

Sounds good Daniel.

Note that there are a bunch of other package managers that we will also want to include here.

What other package managers do you recommend including?

@waderyan
Copy link

Will the old download experience for RPM no longer work? (i.e. when we release next week will users be blocked from being able to download RPM?)

@Tyriar
Copy link
Member Author

Tyriar commented Feb 23, 2017

We can stick with yum for now and add them over time but zypper is another common one.

Downloading the package will still work but it won't let you auto-update, so we want to steer people towards the repository.

@Tyriar
Copy link
Member Author

Tyriar commented Mar 1, 2017

I updated the instructions in 261469d. Now we just need to old rpm package download links on the home page to point at https://code.visualstudio.com/docs/setup/linux#_installation, @waderyan would you be able to handle that for me? It would probably be fine to keep the download icon as is as well, that's still what they're going to be doing just the package manager will handle the download now.

As for the download page, we probably want to change that too but I'm not sure how just yet since we also want to expose all existing download methods for people who need 32-bit, a tarball or just need to download the package to install offline. I'm fine with deferring changing https://code.visualstudio.com/Download until after we publish 1.10 since it might involve some bigger changes.

@ismail
Copy link

ismail commented Mar 1, 2017

Submitted #866 for openSUSE/SLE instructions.

@waderyan
Copy link

waderyan commented Mar 1, 2017

Step 1 is complete. We now will link to rpm instructions for rpm 64 bit.

@gregvanl gregvanl modified the milestones: February 2017, April 2017 Apr 3, 2017
@gregvanl gregvanl modified the milestones: May 2017, April 2017 May 2, 2017
@gregvanl gregvanl modified the milestones: May 2017, June 2017 Jun 8, 2017
@gregvanl gregvanl removed this from the June 2017 milestone Jun 21, 2017
@gregvanl
Copy link

gregvanl commented May 5, 2018

Closing old issue (no activity in over a year). @Tyriar Let me know if there is still some work required.

@gregvanl gregvanl closed this as completed May 6, 2018
@Tyriar
Copy link
Member Author

Tyriar commented May 6, 2018

@gregvanl this is done 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants