Skip to content

Instantly share code, notes, and snippets.

Forked from mojavelinux/atom-fedora-20.adoc
Created August 20, 2014 19:46
Show Gist options
  • Save CARocha/9ee149ab5fa0f7ac0220 to your computer and use it in GitHub Desktop.
Save CARocha/9ee149ab5fa0f7ac0220 to your computer and use it in GitHub Desktop.

Using Atom on Fedora 20

This guide walks you through the steps of building and launching the Atom text editor on Fedora 20.

Building Atom

  1. Install prerequisite packages

    $ sudo yum -y install node npm libgnome-keyring-devel
  2. Install Chrome (needed for

    $ sudo sh -c 'cat > /etc/yum.repos.d/google-chrome.repo <<EOS
     sudo yum -y install google-chrome-stable
  3. Upgrade npm locally (Fedora packages 1.3.6, but version 1.4 is required)

    $ cd ~
      npm install npm
  4. Ensure the local npm bin location is on your PATH

    $ export PATH="$HOME/node_modules/.bin:$PATH"
  5. Open a new terminal window to reset the path to npm

    $ npm --version
    # 1.4.10
  6. Uninstall gyp package (which also removes npm and node-gyp) to avoid gyp / node-gyp conflicts

    $ sudo yum -y remove gyp
    For more information about this problem, see issue #2029.
  7. Clone the Atom repository and switch to it

    $ git clone
      cd atom
  8. Build Atom (writes to build and /tmp/atom-build)

    $ ./script/build
    Disregard any compiler or npm warnings.
  9. Make the atom binary executable

    $ chmod +x /tmp/atom-build/Atom/atom
  10. (Optional) Reinstall the node-gyp package (if needed for system operations)

    $ sudo yum -y install node-gyp

Launching Atom

$ LD_LIBRARY_PATH=/opt/google/chrome ./

Relocating the Atom installation

If you want to relocate the Atom installation outside of the /tmp directory, run the following commands:

$ mkdir -p ~/apps/atom/share
  mv /tmp/atom-build/Atom ~/apps/atom/share/atom
  cp ~/apps/atom/share/

Now you can run Atom using the following command:

$ LD_LIBRARY_PATH=/opt/google/chrome ~/apps/atom/share/

Write code!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment