setting up hyperkitty dev environment

Stumbled across one of Fedora’s app called HyperKitty and was interested in some of their UI. To get started mucking around with the code, I followed these directions to setup the dev environment. I used a Fedora 19 image running on VMWare. The only changes I needed to do were:

• Run all the software updates for Fedora before doing any of the dev setup steps.
• Set up a Launchpad account and a GitHub account
• Create a SSH key and add it to your accounts. To create a SSH key:

  # create ssh keys
  ssh-keygen -t rsa
  chmod 700 ~/.ssh
  chmod 600 ~/.ssh/id_rsa
  chmod 644 ~/.ssh/id_rsa.pub

• Tell bzr my launchpad id:

  bzr launchpad-login <launchpad-username>

• Configure git:

  sudo yum install meld # meld will be our merge tool
  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"
  git config --global core.editor nano
  git config --global merge.tool meld
  

When running the various python setup.py install commands, I ran into the following error message:

unable to execute gcc: No such file or directory
error: Setup script exited with error: command 'gcc' failed with exit status 1

To solve this, I just installed gcc (sudo yum install gcc). (Note that, by following the Development Setup Guide and running the install command after trying to setup mailman, that means that gcc gets installed inside the virtualenv. It’s easy enough to run the install command again outside the virtualenv.) Other helpful tips:

• To exit out of a virtualenv, just deactivate it. In my case, that meant going to a terminal window that was running the virtualenv (as indicated by the (mailman) prefix in front of the prompt, and typing deactivate. It’s also possible to just delete the virtualenv directory. In my case, this would mean removing mailman/lib and mailman/bin.
• If you open a new terminal window and want to stay in the virtualenv, then just reactivate it. In my case, I just run the command: source mailman/bin/activate