[WIP] Installation scenarios for the CLI - spec #1482

blackdwarf · 2016-02-18T23:04:10Z

Add stuff and rename the file.

/cc @piotrpMSFT @krwq @brthor @Sridhar-MS

Documentation/cli-installation-scenarios.md

+- All installers are signed properly 
+- Upgrades using the native installers Just Work(tm)
+- All user facing materials point to the getting started page
+- The user needs extra effort to install the "bleeding edge" bits


krwq · 2016-02-18T23:34:29Z

this is WIP, please do not merge yet

Documentation/cli-installation-scenarios.md

+Channels also impact the NuGet packages. Based on the version of the package specified, the user may end up getting different channels. This is described in more details in [Nuget Packages section](#nuget-packages).  
+
+# Dependencies
+.NET Core CLI is built on top of CoreFX and CoreCLR and as such its' dependencies set is defined by the platform that those two combine. Some of the install options provide an automatic way to install these dependencies, while other do not. However, it is important to note that the CLI bundle will **not carry those dependencies with it** in any case. This means that for those install options that do not support automatic 


TheRealPiotrP · 2016-02-19T00:16:39Z

@mmitche Azure0211103841 is out of space.

mmitche · 2016-02-19T00:18:00Z

@piotrpMSFT When you see this for machines starting with Azure, just log and delete the machine

TheRealPiotrP · 2016-02-19T00:19:48Z

@dotnet-bot test Ubuntu Debug Build please.

TheRealPiotrP · 2016-02-19T00:20:01Z

@dotnet-bot test Ubuntu Release Build please.

TheRealPiotrP · 2016-02-19T00:20:11Z

@mmitche fantastic!

mmitche · 2016-02-19T00:21:19Z

@piotrpMSFT What's odd is that we did manage to run out of space. I wonder if there was a test run that really killed some disk space.

TheRealPiotrP · 2016-02-19T00:22:48Z

If we see it often, let's take a look at an instance machine.

blackdwarf · 2016-02-19T03:31:17Z

@krwq can you please take a stab at the NuGet section? You can actually, I think, push to this branch as well. :)

Documentation/cli-installation-scenarios.md

+
+# General principles
+
+- All installers are signed properly 


Documentation/cli-installation-scenarios.md

+* Support for specifying the version
+* Support for specfying the installation location
+* Support specifying whether the debug package needs to be downloaded
+


blackdwarf · 2016-02-20T19:13:59Z

@piotrpMSFT new version is up.

Documentation/cli-installation-scenarios.md

+|-------------------------------	|-----------------------------	|--------------	|-----------------------------------------------------------------------------------------------------------------------------	|
+| --channel                     	| -Channel                    	| "Production" 	| Which channel (i.e. "nightly", "preview", "production") to install from.                                                    	|
+| --version                     	| -Version                    	| Latest       	| Which version of CLI to install; you need to specify the version as 3-part version (i.e. 1.0.0-13232). Also it is possible to use "latest" and "lkg" to point to latest and latest known good build                       	|
+| --prefix                      	| -InstallDir                 	| ./dotnet     	| Path to where to install the CLI bundle. The directory is not created if it doesn't exist.                                  	|


TheRealPiotrP · 2016-02-26T23:05:02Z

Some additional feedback:

Latest should be global.json, then Latest
dotnet-install.ps1/sh for consistency
default install path: per-User

blackdwarf · 2016-02-26T23:20:33Z

@piotrpMSFT the default install path is .dotnet in the place where the thing was invoked. Are you saying this should be .dotnet in $HOME?

TheRealPiotrP · 2016-02-26T23:28:27Z

@blackdwarf that's the idea. Any concerns?

Documentation/cli-installation-scenarios.md

+
+| Channel    	| Branch    	| Debian feed 	| Debian package name 	| NuGet version 	| NuGet feed                            	|
+|------------	|-----------	|-------------	|---------------------	|---------------	|---------------------------------------	|
+| Nightly    	| master    	| Development 	| dotnet-nightly      	| 1.0.0-dev-*   	| https://dotnet.myget.org/f/dotnet-cli 	|


blackdwarf · 2016-02-27T00:01:31Z

@piotrpMSFT yep and no. Nothing against the overall idea, but would like the install.ps1 to use the proper Windows location for the folder rather than $env:HOME. This is %LocalAppData%.

blackdwarf · 2016-02-27T05:10:22Z

@piotrpMSFT @krwq new version is up.

blackdwarf · 2016-02-28T20:34:16Z

@piotrpMSFT actually, I really don't like the name dotnet-install. Would be better to reverse it and call it install-dotnet.

blackdwarf · 2016-03-01T07:47:53Z

@dotnet-bot test Windows_NT Release Build please

Documentation/cli-installation-scenarios.md

+Obtaining .NET CLI 
+==================
+
+# Contents


…rios.md

[WIP] Installation scenarios for the CLI - spec

dnfclas added the cla-already-signed label Feb 18, 2016

leecow added the in progress label Feb 18, 2016

krwq reviewed Feb 18, 2016
View reviewed changes

TheRealPiotrP reviewed Feb 19, 2016
View reviewed changes

Documentation/cli-installation-scenarios.md

# General principles

- All installers are signed properly

This comment was marked as spam.

Sign in to view

This comment was marked as spam.

Sign in to view

TheRealPiotrP reviewed Feb 20, 2016
View reviewed changes

Documentation/cli-installation-scenarios.md

* Support for specifying the version

* Support for specfying the installation location

* Support specifying whether the debug package needs to be downloaded

This comment was marked as spam.

Sign in to view

krwq reviewed Feb 26, 2016
View reviewed changes

This was referenced Feb 29, 2016

Fix CLI upgrade bug aspnet/Universe#383

Closed

Do not download a pinned version of cli if it is already installed. #1630

Merged

blackdwarf force-pushed the blackdwarf-patch-1 branch from 371445b to f329ae2 Compare March 2, 2016 06:06

khellang reviewed Mar 2, 2016
View reviewed changes

Documentation/cli-installation-scenarios.md

Obtaining .NET CLI

==================

# Contents

This comment was marked as spam.

Sign in to view

blackdwarf force-pushed the blackdwarf-patch-1 branch from f329ae2 to 9057c03 Compare March 2, 2016 15:33

Update and rename installation-scenarios.md to cli-installation-scena…

fb10268

…rios.md

blackdwarf force-pushed the blackdwarf-patch-1 branch from 9057c03 to fb10268 Compare March 3, 2016 01:27

blackdwarf pushed a commit that referenced this pull request Mar 3, 2016

Merge pull request #1482 from dotnet/blackdwarf-patch-1

771f4ed

[WIP] Installation scenarios for the CLI - spec

blackdwarf merged commit 771f4ed into rel/1.0.0 Mar 3, 2016

blackdwarf deleted the blackdwarf-patch-1 branch March 3, 2016 01:28

leecow removed the in progress label Mar 3, 2016

[WIP] Installation scenarios for the CLI - spec #1482

[WIP] Installation scenarios for the CLI - spec #1482

Conversation

blackdwarf commented Feb 18, 2016

This comment was marked as spam.

This comment was marked as spam.

krwq commented Feb 18, 2016

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

TheRealPiotrP commented Feb 19, 2016

mmitche commented Feb 19, 2016

TheRealPiotrP commented Feb 19, 2016

TheRealPiotrP commented Feb 19, 2016

TheRealPiotrP commented Feb 19, 2016

mmitche commented Feb 19, 2016

TheRealPiotrP commented Feb 19, 2016

blackdwarf commented Feb 19, 2016

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

blackdwarf commented Feb 20, 2016

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

TheRealPiotrP commented Feb 26, 2016

blackdwarf commented Feb 26, 2016

TheRealPiotrP commented Feb 26, 2016

This comment was marked as spam.

This comment was marked as spam.

This comment was marked as spam.

blackdwarf commented Feb 27, 2016

blackdwarf commented Feb 27, 2016

blackdwarf commented Feb 28, 2016

blackdwarf commented Mar 1, 2016

This comment was marked as spam.