Output should mention installation method

[Daniel15]

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
When running yarn commands, it includes the version number:

$ yarn install
yarn install v0.15.0
info No lockfile found.
success Nothing to install.

This is very useful, particularly with bug reports (as anyone that includes the full output with the bug report will automatically include the version number.

What is the expected behavior?
It would be useful to also include the installation method in that output. For example, when installed from the Debian/Ubuntu repo:

$ yarn install
yarn install v0.15.0-deb
info No lockfile found.
...

Similarly, when installed via Windows installer:

yarn install v0.15.0-msi

Or from tarball:

yarn install v0.15.0-tarball

Some bugs are specific to certain installation methods, so we end up having to ask "Did you install through the Ubuntu package, the tarball, or npm?" in some bug reports.

This would require the packaging scripts to make a modification to some file to signify the installation method, and something at runtime to read that file.

[FLGMwt]

Should every run of a program optimize for but reports, or would maybe this enchancement and the version declaration as it exists be reserved for a yarn --version?

[Daniel15]

I figured that it doesn't add much overhead so it's fine always displaying it wherever we show the version, but only displaying the info on yarn --version is a good idea.

[olingern]

@Daniel15 To continue with your examples, there are a number of ways to get Yarn. So, are you thinking something like the following?

tarball
yarn install v0.15.0-tarball

brew
yarn install v0.15.0-brew

msi
yarn install v0.15.0-msi

Chocolatey
yarn install v0.15.0-choco

CentOS / Fedora / RHEL
yarn install v0.15.0-rpm

Solus
yarn install v0.15.0-eopkg

Arch Linux
yarn install v0.15.0-aur

Shell Script
yarn install v0.15.0-sh

npm
yarn install v0.15.0-npm

[Daniel15]

@olingern - Tarball and shell script are essentially the same (the shell script just downloads and extracts the tarball). Right now, the Solus and Arch packages are not official, I'm not sure how those packages are being built (probably using the tarball) so I don't know how we'd record the installation method for those. Maybe I'll look into how those packages are built, and add them to our official build scripts.