From Sugar Labs
Jump to navigation Jump to search

This is a short guide to show how you can contribute with the Sugar project in a simple way, without dealing with sugar-jhbuild, installing libraries and compiling weird things. You can work directly on a Stick (USB Pen Drive). Even more, if you want to work faster on your real computer you can run it inside a Virtual Machine with qemu-kvm

In the below sections are shown the steps that you have to follow to get a complete working Virtual Machine with all the necessary things to start collaborating.

NOTE: I made this guide on Fedora 17 and if you are using another distro maybe the name of the packages change

Packages needed

These are the packages needed to run the Virtual Machine with qemu-kvm

sudo yum install qemu qemu-kvm qemu-kvm-tools

Sugar On A Stick Image

This is the image (32-bits) that you should download to install it on the Virtual Machine.

Booting Sugar from the USB on a Virtual Machine

  • Create the virtual hard disk drive:
qemu-img create -f qcow2 sugar-on-a-stick.qcow2 4G
  • Run the virtual machine
qemu-kvm -hda qcow2 sugar-on-a-stick.qcow2 -m 1024 -cdrom Fedora-17-x86_64-Live-SoaS.iso -boot d

Installing Sugar on the hard drive

  • After running the last command and setting up your name you will be on Sugar itself
  • Open Terminal Activity and click on the Become root icon or type su -
  • Run this command to lunch the installer
  • When the installer opens and you reach the partitioning part you have to select to do it manually and create just one partition with the full space available (4Gb) because otherwise the installer will tell you there is no sufficient space to copy the files required by Fedora 17
  • Follow the installation instruction and finally reboot the Virtual Machine

Running Sugar from the Virtual Machine

qemu-kvm -hda sugar-on-a-stick.qcow2 -m 1024 -k es

Install useful packages

sudo yum install git vim emacs

NOTE: add some information here about how to edit a file and create a patch, maybe downloading the git repo or the simplest case, editing the original activity directly. Add some useful links to code review o those kind of things