Support naming variations for google-chrome on linux

[jevonearth]

Different distros package google-chorme with different names.

Ubuntu: google-chrome
Arch: google-chrome-stable

Would be nice if launchpad check for several common variations.

[alan-morey]

Assuming you have the google-chrome-stable package installed under Ubuntu, then both google-chrome-stable and google-chrome are symlinks under /usr/bin.

Symlinks as follows:

/usr/bin/google-chrome -> /etc/alternatives/google-chrome -> /usr/bin/google-chrome-stable ->  /opt/google/chrome/google-chrome

[mazswojejzony]

Starting with 0.5.0 you can define path to e..g Chrome like this: LAUNCHPAD_CHROME=path/to/chrome. See docs.

[mattyclarkson]

The LAUNCHPAD_CHROME is a work around but requires me to set that up on all my build slaves. Can the project do something similar to karma-chrome-launcher in that it falls backwards through the browser names.

You could change this line to support an array and each is done in turn. Or add a key called executables so that the dictionary looks like:

  chrome: {
    pathQuery: 'which ${executable}',
    executables: ['chromium-browser', 'chromium', 'chrome', 'google-chrome'],
    process: 'chrome',
    opensTab: true,
    args: ['--no-first-run']
  },

And the search runs through each of the executables replacing ${executable} in the pathQuery?

It would be a great usability win if launchpad just fired up on GNU/Linux distros by default like Karma.

[daffl]

This can probably be done fairly easy by changing the pathQuery at https://github.com/ekryski/launchpad/blob/master/lib/local/platform/unix.js#L5 to 'which chromium-browser chromium chrome google-chrome'. Always open for PRs.