Add Debian and Ubuntu build + package repo

[Daniel15]

Ubuntu is by far the most popular Linux distribution, so I think a fairly large portion of Yarn users will be using it in their development environment (often via Docker or Vagrant). We should build Debian/Ubuntu packages as part of the build, to allow users to simply do apt-get install yarn to install it, and their regular system updates (apt-get update && apt-get upgrade ) will keep it up-to-date.

We should also consider a Chocolatey package for Windows users, but that can go in a separate task.

Examples of what other projects do:

• HHVM have Ubuntu and Debian packages in their own custom repo (http://dl.hhvm.com/). Installation instructions: https://docs.hhvm.com/hhvm/installation/linux
• Atom do not have a package repository, however they do build .rpm, .deb, .nupkg and Windows installers for every release, and post them to Github releases for every release: https://github.com/atom/atom/releases/latest. There's an unofficial repo maintained by Webupd8 here: https://launchpad.net/~webupd8team/+archive/ubuntu/atom
• Microsoft have Ubuntu packages in their own custom repo for .NET Core: https://www.microsoft.com/net/core#ubuntu

Advantages of using the system's native package manager rather than something like npm install -g yarn:

• Upgrades are handled the same way as all other software on your system (apt-get upgrade). It's not a special snowflake.
• All the security problems with npm (eg. packages not being signed) make it less than ideal for anything installed system wide. apt-get gives you proper GPG signature verification.
• Using npm means you're tightly-coupled to npm. If you later want to have a better installation solution, you need to have this awkward transition period where you try to get users to switch to the newer installation method.
• The setup instructions need the whole weird "install Node.js first, then ensure npm is up-to-date, then install Yarn" thing. That'd be like telling people to manually install their npm dependencies 😆 . With a proper package management system, the Yarn package would simply have a dependency on the Node.js package, and "apt-get install yarn" would install both.

If we want to appeal to people that have limited Node.js experience, we shouldn't make any assumptions that they know anything about the Node.js ecosystem or what "npm" even is.

[cpojer]

Let's have this discussion in #275.

[Daniel15]

Oops, I searched and missed that! Sorry @cpojer!

[bestander]

We build rpm for Linux internally at FB.
I wonder if we could share the build script

On Wednesday, 21 September 2016, Daniel Lo Nigro notifications@github.com
wrote:

Ubuntu is by far the most popular Linux distribution. We should build
Debian/Ubuntu packages as part of the build, to allow users to simply do apt-get
install yarn to install it, and their regular system updates (apt-get
update && apt-get upgrade ) will keep it up-to-date.

We should also consider a Chocolatey package for Windows users, but that
can go in a separate task.

Examples of what other projects do:

• HHVM have Ubuntu and Debian packages in their own custom repo (
  http://dl.hhvm.com/). Installation instructions:
  https://docs.hhvm.com/hhvm/installation/linux
  https://docs.hhvm.com/hhvm/installation/linux
• Atom do not have a package repository, however they do build .rpm,
  .deb, .nupkg and Windows installers for every release, and post them
  to Github releases for every release: https://github.com/atom/atom/
  releases/latest. There's an unofficial repo maintained by Webupd8
  here: https://launchpad.net/~webupd8team/+archive/ubuntu/atom
  https://launchpad.net/%7Ewebupd8team/+archive/ubuntu/atom
• Microsoft have Ubuntu packages in their own custom repo for .NET
  Core: https://www.microsoft.com/net/core#ubuntu

Advantages of using the system's native package manager rather than
something like npm install -g yarn:

• Upgrades are handled the same way as all other software on your
  system (apt-get upgrade). It's not a special snowflake.
• All the security problems with npm (eg. packages not being signed)
  make it less than ideal for anything installed system wide. apt-get gives
  you proper GPG signature verification.
• Using npm means you're tightly-coupled to npm. If you later want to
  have a better installation solution, you need to have this awkward
  transition period where you try to get users to switch to the newer
  installation method.
• The setup instructions need the whole weird "install Node.js first,
  then ensure npm is up-to-date, then install Yarn" thing. That'd be
  like telling people to manually install their npm dependencies 😆 .
  With a proper package management system, the Yarn package would simply have
  a dependency on the Node.js package, and "apt-get install yarn" would
  install both.

If we want to appeal to people that have limited Node.js experience, we
shouldn't make any assumptions that they know anything about the Node.js
ecosystem or what "npm" even is.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#385, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBdWOCzzu5EwUfev6K2tA-0BFbUdG1nks5qsLr2gaJpZM4KCZ1H
.