Meego Wiki
Views

User:Stskeeps/MeeGo Hacker Guide

From MeeGo wiki
< User:Stskeeps
Revision as of 11:37, 27 October 2010 by Sivan (Talk | contribs)
Jump to: navigation, search

DRAFT

Hands On: Setting up your workshop

You'll need:

  • An OBS account on either build.meego.com or cbuild.meego.com (use your meego.com login) or on your own OBS with MeeGo release(s) imported.
  • These tools installed on your development machine:
    • Spectacle, autospectacle (on gitorious)
    • MIC2
    • osc
    • Standard development tools (git, wget, svn, make, diff, patch, rsync, ssh, dd, gdb)
    • A graphical web browser (Firefox, Chrome, etc..)

You might need:

  • For local OBS builds, something supporting SSSE3 instructions (this applies for ARM builds too)
  • qemu-arm installed, vdso=0

.. tools to grab images/releases? .. zypper instructions .. proxy instructions, NAT wlan


Theory: Stuff which will make life easier, engage, and profit properly understood

  • Background of the user-space and middle ware stack:
    • The context of the current middle ware discussed.
    • What's beneath it (another layer, the bare metal?), What's on top of it?
    • Nature of inter-relationships: How does it communicate with other components if at all? How does it communicate with hardware?
  • Breakdown to subsystems:
    • Each component have a section with links or content to:
      • Read about the architecture.
      • Libraries and binaries it uses,
      • Current important bugs for triage and fixing, tagged with difficulty level.
      • Find out where offline development discussions happen.
      • Learn about low hanging fruits; not just bug fixing and feature implementation!
  • Background for the UI parts and perhaps follow the same breakdown as for (2) ??
  • Each component resulting in a binary should have links to the proper documentation for it, or a mention where docs are in the RPM packages itself.

IRC dumps of what could become part of documentation, even if somewhat explained in other places

11:57 < timoph> I'm using repo.meego.com to get the tools 11:57 < timoph> deb http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/ / 11:57 < timoph> in sources.list 11:58 * sivang adds 11:58 < timoph> the install osc osc-meego-plugins build 11:58 < timoph> s/the/then/ 11:59 < timoph> (might need something else too) 12:00 < timoph> after installing osc do 'osc -A http://api.cbuild.meego.com ls' and add your credentials 12:01 < timoph> and edit ~/.oscrc (change su-wrapper to use sudo) 12:01 < sivang> where's the key for apt? 12:01 < sivang> it complains about unauthenticated sources 12:01 < timoph> http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/Release.key 12:01 < sivang> thanks 12:03 < sivang> timoph: key imported 12:03 < sivang> E: Couldn't find package osc-meego-plugins 12:03 -!- asinnela [~arsinnel@gw2.digia.com] has joined #meego-qa-tools 12:03 < timoph> you can also 'sudo visudo' and append '[your username] ALL=NOPASSWD: /usr/bin/build' 12:04 < timoph> hmmh. did you do run apt-get update ? 12:04 < sivang> I did, I'll rerun 12:05 < timoph> you can live without the meego-plugins if they're not available 12:05 < timoph> ahh. sorry 12:05 < timoph> it's 'meego-osc-plugins' 12:07 < timoph> have you created your home project? 12:07 -!- petrik [~chatzilla@nat/nokia/x-slqkpgymlbhyqzfn] has joined #meego-qa-tools 12:08 < timoph> after you have created your home project you can checkout it and start creating packages 12:09 < timoph> osc co home:[username] 12:09 < timoph> you'll need to add files to the project before building them e.g. 'osc add some.spec' 12:09 -!- dneary [~dneary@ALyon-152-1-57-212.w86-193.abo.wanadoo.fr] has joined #meego-qa-tools 12:09 -!- dneary [~dneary@ALyon-152-1-57-212.w86-193.abo.wanadoo.fr] has quit [Changing host] 12:09 -!- dneary [~dneary@Maemo/community/docmaster/dneary] has joined #meego-qa-tools 12:10 < timoph> to build locally do 'osc build --no-verify' 12:10 < timoph> easiest way to get started is to take some existing package and play with it 12:11 < timoph> you can copy packages from other user's projects to your home by 'osc copypac home:someuser package

               home:yourusername'

12:12 < sivang> timoph: okay, pluging installed. Now that ':' notation, this is what you refer to all the time with

               Trunk:Tools etc?

12:12 < sivang> timoph: what's a home project in that regard? 12:13 < timoph> your own home project 12:13 < timoph> in obs

Personal tools