User:Jaffa/Jumpstart
m |
(not on gconf-key for browser) |
||
(2 intermediate revisions not shown) | |||
Line 3: | Line 3: | ||
|- | |- | ||
| | | | ||
+ | # Move workspace to <code>/scratchbox/users/maemo/home/maemo/workspace</code> and symlink back to <code>~/workspace</code> | ||
# Install Hermes through HAM in Scratchbox | # Install Hermes through HAM in Scratchbox | ||
+ | ## or fix dependencies: python-twitter python-facebook python-evolution python-simplejson | ||
+ | ## and postinst: gconf-key for browser | ||
# Install <code>git-core git-gui gitk community-themes</code> in VM | # Install <code>git-core git-gui gitk community-themes</code> in VM | ||
# Change theme to ''New Wave'' | # Change theme to ''New Wave'' |
Latest revision as of 20:56, 6 June 2010
TODO |
---|
|
Contents |
[edit] Getting started
The Hermes repository needs "cloning" to your environment. Open Terminal and type:
$ cd workspace $ git clone git://bleb.org/ hermes.git
We then need to tell git about you:
$ git config --global user.name "Joe Bloggs" $ git config --global user.email "jbloggs@example.com"
Finally, we import the project into Eclipse:
- Start ESBox
- Select File > Import... > General > Existing project into workspace...
- Browse to
~/workspace/hermes.git
- Ensure Hermes is checked.
- Click Finish.
[edit] Starting Maemo
From within ESBox click the drop down next to the Maemo ae and select Start.
[edit] Starting Hermes
TBC!
[edit] Development
[edit] Committing changes
When there are changes in your working copy. git needs to be told that you want to commit the changes to these files (and that "Usage.txt" is a new file it should care about):
$ cd ~/src/hermes.git $ git status $ git add Logos/Usage.txt Logos/bg-transparent.png $ git status
Finally, commit the changes to your local branch with an appropriate commit message:
$ git commit -m "Tweak PNG logo, and add usage guidelines"
You can use git log
and GUI tools like gitk
to explore the branch on your harddisk, and see the changes over time.
When should you commit?
Commit when a "chunk" of work has been completed, and make each commit contain files which are related.
[edit] Pushing changes
It is important to push your changes back up to the master repo, as this then makes them available for "pulling" by anyone else on the project:
$ git push origin master
origin is the name of your local branch, and master is the name of the remote branch.
[edit] Pulling changes
Similarly, other people may have made changes which you should be aware of. You can retrieve them by doing:
$ git pull origin master
- This page was last modified on 6 June 2010, at 20:56.
- This page has been accessed 2,978 times.