Community Office/Community device program/Nokia/Development repos

2011-07-31T18:23:22Z

Djszapi: /* Applications */

The [[MeeGo Apps|"Apps" process]] is one of developers having individual repositories for building/testing their apps; and once at a stable enough quality promoting them to a shared Apps-testing repository. Once the [[MeeGo Apps/QA]] process has been followed, the packages will be promoted to the Apps repo.

However, whilst that process gets worked out, developers may want to assist in testing each others' software. In terms of coordinating porting of libraries, see the ''Intent To Package'' page: [[Build Infrastructure/Community Builder/ITP]].

The following lines should be added to <code>/etc/apt/sources.list.d</code> in a file called <code>nick.list</code>. You can browse the packages in each one by visiting it in a web browser and looking in <code>all</code> and <code>armel</code>:

To create your own repository, see [[Getting started with OBS]].

== Apps & Apps-testing ==

Not yet ready.

== Applications ==
deb http://harmattan-dev.nokia.com/ harmattan/sdk free non-free
deb http://repo.pub.meego.com/home:/rzr:/harmattan/MeeGo_1.2_Harmattan_Maemo.org_MeeGo_1.2_Harmattan_standard/ ./
deb http://repo.pub.meego.com/home:/CaCO3/Harmattan/ ./
deb http://repo.pub.meego.com/home:/andreagrandi/Harmattan/ ./
deb http://repo.pub.meego.com/home:/elleo/Harmattan/ ./
deb http://repo.pub.meego.com/home:/fiferboy/Harmattan/ ./
deb http://repo.pub.meego.com/home:/jaffa/Harmattan/ ./
deb http://repo.pub.meego.com/home:/khertan/Harmattan/ ./
deb http://repo.pub.meego.com/home:/nimnes/Harmattan/ ./
deb http://repo.pub.meego.com/home:/spenap/Harmattan/ ./
deb http://repo.pub.meego.com/home:/vgrade:/twingo/Harmattan/ ./
deb http://sheeplauncher.net/debs/ ./

== Libraries & tools ==

deb http://repo.pub.meego.com/home:/jokylanp/MeeGo_1.2_Harmattan/ ./
deb http://repo.pub.meego.com/home:/sandst1:/harmattan/MeeGo_1.2_Harmattan/ ./
deb http://repo.pub.meego.com/home:/tjyrinki/harmattan/ ./

Community Office/Community device program/Nokia/Development repos

2011-03-06T12:57:54Z

Djszapi: Build speed up note

== Introduction ==

This guide is a way to build packages for the MeeGo 'day one' release, before more proper developer tools are introduced.

== Setting up your development environment ==

To begin developing for the MeeGo 'day one' release, you will need to follow these steps:

* NOTE: These instructions were tested on a Fedora 12 chroot (X86), your experience may vary with other distributions.
* Have access to 'root' on your development machine.
* [http://wiki.meego.com/Image_Creation#Requirements Satisfy the requirements for MIC2 installation]
* [http://wiki.meego.com/Image_Creation#Installation Download MIC2 from the git repository] (development tree)
* [http://wiki.meego.com/Image_Creation#Installation Install MIC2]
* For ARM, Install QEMU: Grab the qemu package for your system. Fedora one is at [http://build.moblin.org/build/devel:tools:building/Fedora_11/i586/qemu/qemu-arm-static-0.12.3-10.1.i386.rpm this url]
* After this, run 'qemu-binfmt-conf.sh' as root. This will enable your system to run ARM binaries and will have to be repeated at system startup.
* If you have Scratchbox and/or Maemo SDK installed, please follow [http://wiki.maemo.org/Mer/Build/Application_Building#Co-existing_with_Scratchbox these instructions to avoid conflicts]
* Download MeeGo development images for [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-ia32-developer-201003311106.img.bz2 MeeGo X86] and [http://repo.meego.com/MeeGo/devel/n900/images/meego-codedrop-arm-developer-201003311152.img.bz2 MeeGo ARM] and bzip2 -d them (they are 3GB loopback images)
* Or you can create your own development images with [[Media:Devel-ia32.ks|this kickstart file for X86]] or [[Media:Devel-arm.ks|this kickstart file for ARM]] and the instructions at [[Image_Creation_For_Beginners]]

== Introducing the tools ==

=== mic-chroot ===

mic-chroot is a tool that allows you to 'chroot' into an existing MeeGo image in order to develop within it, without contaminating your developer machine's environment. Chroot simply means to 'change the root' to a new location (so instead of your root being / on your dev machine, it will be the new root directory within the image).

This restricts access to your real root and your real file system, and instead, uses the image filesystem as its root and filesystem. No contamination, and no effect on your development machine.

With mic-chroot, you will effectively be able to modify and manipulate the image's filesystem as if you were running a shell within an installed image, without having to install the image. When finished, you can also create a new MeeGo image based on your changes.

=== Developer images ===

The developer images contain the exact same packages as is installed when you try to build a package in the MeeGo OBS without any dependencies, along with some helper packages (vim, nano) to make chroot usage easier. The list of these packages can be seen in the kickstart file mentioned above.

This is because, in the end, it will save you time when you want to upload your application into a builder system because it will make sure that you specify your package build dependencies correctly.

You can in the development image chroot run 'yum install <package names>' and that way install your package build dependencies to the chroot to compile your package.

== Building your package: Step by step ==

Prerequisites:

* It is assumed you have already made either a source rpm (.src.rpm) or a package (.spec and attached files) before these steps. For a guide how to create packaging for MeeGo, see [[Packaging]].
* You have already chosen an architecture to build your package towards in these steps. That is the development image <image-name>, either meego-codedrop-ia32*.img (X86) or meego-codedrop-arm*.img (ARM)

=== Step 1: Chrooting into the development image ===

<pre>
sudo mic-chroot <image-name>
</pre>

With this command, you are now transported into the root filesystem of the image. It is possible to exchange files with your normal file system through the /parentroot directory. You can also conduct yum install, yum remove and any other network related operations.

Note: You can install the cross-compiler in order to speed up the build procedure (Basically that is what the OBS also uses):
<pre>
zypper install cross-armv7l-binutils-accel-armv7l cross-armv7l-gcc-accel-armv7l glibc-x86-arm
</pre>

=== Step 2: Setting up the build directories ===

You only need to do this once, but you may want to clean up the directory and remake it once in a while.

<pre>
mkdir -p ~/rpmbuild
cd ~/rpmbuild
mkdir -p SOURCES SPECS BUILD RPMS SRPMS
</pre>

=== Step 3: Staging source package for build ===

You must change directory to the location of your sources.

<pre>
cd /parentroot/path/to/your/sources
</pre>

If you have a source rpm (.src.rpm), you will need to extract it:

<pre>
rpm2cpio <MyPkg>.src.rpm | cpio -idmv --no-absolute-filenames
</pre>

This will result in a .spec file and maybe some attached files (patches, source tarball, etc). The .spec file is in this guide called package.spec.

When you have a .spec file you need to place it in ~/rpmbuild/SPECS and the remaining files in ~/rpmbuild/SOURCES.

=== Step 4: Installing your build dependencies ===

You can see your build dependencies in the package.spec file, which is the lines starting with BuildRequires. Those packages can then be installed using 'yum install':

<pre>
yum install <package names>
</pre>

=== Step 5: Building your package ===

To build your package, you must then run the following command, where package.spec is the name of your spec file:

<pre>
rpmbuild -ba ~/rpmbuild/SPECS/package.spec
</pre>

=== Step 6: Enjoying your built package ===

Provided the build completed without errors, you can now see the resulting rpms in ~/rpmbuild/RPMS/. You can transfer these back to your filesystem through the /parentroot directory and you can then transfer these to your MeeGo device, virtual machine, etc and install them there.

== Including your packages in a MeeGo image ==
Before reading these sections, we suggest to first read [[Image Creation For Beginners]] and [[Image Creation]]

This will give you the basics of what you need to generate a basic MeeGo image.

Specifically, there are important details about how to modify a .ks file here: [[Image_Creation#Modifying_your_.ks]]

KickStart .ks files are the main configuration file that the Image Creator uses to create images, and the brunt of what is talked about in this section has to do with modifying your .ks file.

=== Recreating a standard MeeGo Image ===
To create a standard MeeGo image, please follow the instructions in [[Image Creation For Beginners]].

=== Adding more MeeGo packages to a MeeGo Image ===
Here is a scenario where you want to add additional MeeGo packages to the standard MeeGo image.

First, obtain a standard MeeGo .ks file [http://repo.meego.com/MeeGo/ from here]

Check the [http://repo.meego.com/MeeGo/ MeeGo repos] and make sure that the packages you're looking doesn't already exist in MeeGo

Now within the .ks file, add the MeeGo package names that you want included in this new image. For more on how add packages in a .ks file, please read this important section here: [[Image_Creation#Modifying_your_.ks]]

Run this modified .ks file through the Image Creator MIC.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

=== Adding your own code & and non-MeeGo packages to a MeeGo Image ===

If you have your own packages on your developer machine that you want to test out by creating a new MeeGo image with them.

First obtain a standard MeeGo .ks file. This is possible through the repository.

To add a new repo to your .ks file, go here for easy and detailed steps: [[Image_Creation#Modifying_your_.ks]]

Once you add the new repo(s) that the Image Creator will pull from, you now have to list the packages you want to pull down from these repos. For instructions on adding packages to your .ks file, go here: [[Image_Creation#Modifying_your_.ks]]

If you have local rpms on your local machine that you would like to include, you need to first create a local repo on your machine. Move your rpms into a directory. Then create a local repo with that directory like so:

<pre>
$ mv *.rpms /home/user/my-local-repo

$ createrepo -d /home/user/my-local-repo
</pre>

This turns /home/user/my-local-repo into a local repository that you can point your .ks file to. For steps on how to add a new repo, go here: [[Image_Creation#Modifying_your_.ks]]

And again, make sure you have listed in your .ks all the packages you would like to include in your new MeeGo Image.

Now, simply run this new .ks file through MIC, the Image Creator.

<pre>
sudo mic-image-creator -c my-new-ks.ks -f livecd
</pre>

For more options and details on image creation and MIC, go here: [[Image_Creation]]

Your new image will now be a standard MeeGo image including the new packages and repos you've added.

Again, this wiki is of great value to you when manipulating and navigating through .ks files: [[Image_Creation#Modifying_your_.ks]]
It is the key to mastering the art of creating custom-made MeeGo images.

== Troubleshooting (ARM) ==

=== Error: chroot: cannot run command X: No such file or directory ===

Most likely cause: You have Scratchbox1 installed and you need to follow instructions given in Prerequisites for ARM.

=== Exec format error ===

Most likely cause: You have not run qemu-binfmt-misc.sh as root.

Maybe qemu-arm is not right set,try :
<pre>
rpm -i http://download.opensuse.org/repositories/home:/dl9pf:/qemu/Fedora_12/i386/qemu-devel-0.13git2010.06.24.1826-8.1.i386.rpm
</pre>
(the package maybe changes,so you can go the web address to get it ,then install it )
see here:[[Local_Build_Without_OBS_Needed]]

=== mmap: permission denied ===

Most likely cause: VDSO

Do this as root:

<pre>
echo 0 > /proc/sys/vm/vdso_enabled
echo 4096 > /proc/sys/vm/mmap_min_addr
</pre>

Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI

2010-12-21T08:06:27Z

Djszapi: Add Laszlo Papp (djszapi) to the Hacker Team

<div style="float:right;background-color:#fff;width:300px;height:250px;border: solid 1px #ddd;padding:15px;font-size:1.3em;">Sponsors:<ul style="list-style:none;"><li>[[File:Ixonos-logo.gif]] (Main Sponsor)</li><li>[[File:Tieto.jpg]]</li></ul></div>

= Developer to developer =
Tampere initiated the first [[Local_MeeGo_Networks|Local Meego Network]] in Europe, [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere Meego Network]. This is annual summit which is held in different locations around Finland. Tampere will host the first Regional Meego Summit in the world. Although the first Summit is at Tampere, this is a joined effort.

'''[http://www.meetup.com/Tampere-MeeGo-Network/ Tampere] and [http://www.meetup.com/Helsinki-MeeGo-Network/ Helsinki] local networks have joined forces and other local networks are also welcome to participate! Furthermore, this conference will host Finnish hacker & OSS event ''Finhack'' (16th Apr) '''

The summit is open, but the amount of seats is limited!

Meego Summit FI includes also a 'hackathon' type of competition, which includes two categories: 'Hard Core' (Both HW and SW) and 'Quick & Dirty' (Just SW). Competition is called: "Meegathon" and more details can be found below.

== Details ==
* Location: Tampere, Finland. Finlayson area (Plevna, [http://www.uusitehdas.fi/en/ New Factory])
* Time: 15.-16. April 2011
* Duration: 2 days (Fri-Sat)
* Registration fee: Free!
* Seat amount: max 300
* Registration required: yes (address here)
* Web: http://summit.meegonetwork.fi

== Organizers ==
'''Main organizer:'''
{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"|Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Ilkka Lehtinen
| General, sponsors
| Head
| [http://www.coss.fi/en COSS]
|}

'''Co-Organizers:'''

{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"| Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Jarkko Moilanen
| General + Program (Community & hackers)
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Jukka Matikainen
| ?
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Matti Saastamoinen
| General, sponsors
| Organizer
| [http://www.coss.fi/en COSS]
|-
| Ville Kairamo
| Facilities
| Organizer
| [http://www.uusitehdas.fi/en NewFactory]
|}

== Teams ==

=== Program Task-force ===
The committee has been formed by inviting suitable MeeGo Network Finland -community members to it. Current composition is (in alphabetical order):
* [http://meego.com/users/bergie Henri Bergius]
* [http://meego.com/users/jukkaeklund Jukka Eklund]
* [http://meego.com/users/timoph Timo Härkönen]
* [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (Head)

More about the committee work can found [[Meego Summit FI Program|here]]

=== Marketing & PR Team ===
To be formed ASAP.
* [http://meego.com/users/jnwi Jens Wiik]
More information can be found [[Meego Summit FI Marketing|here]]

=== Communication & Tech Team ===
Responsible for:
* Facebook page
* Twitter account
* IRC channel(s) (ops)
* (Future) Portal news and events
* Venue infrastructure & connections
* Mailing lists
* Summit registration (technical)
* ...

'''Members:'''
* [http://meego.com/users/cybette Carol Chen] ([http://twitter.com/cybette @cybette]) - head
* Heikki Ilvespakka? - venue IT head
* [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (kyb3R) - IRC op & chan owner
* ninnnu (wants to participate registration system development)
* your name here


'''Guidelines and policy'''
* Social media: [[Regional_MeeGo_Networks/MeeGo_Network_Finland/Social_Media_Plan | Social Media Plan]]

=== Hosting Team ===
Responsible for:
* helping the speakers
* manages info desk,
* (assists in catering)
* reception/registration (also portal registration development/management).
* ...

'''Members:'''
* add your name here

=== Party Team ===
Responsible for:
* Evening party at MeeGo Summit FI
* ...

'''Members:'''
* add your name here

=== Hacker Team ===
This team will coordinate efforts related to:
* '''Meegathon''' competition which is part of MeeGo Summit FI 2011
* ...

'''Members:'''
* Laszlo Papp (djszapi)
* ...

''' Ideas: '''
* Sign to be attached in the entry-point of Meegathon teams: [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/hackland-sign.png hackland-sign.png]

== Program ==
The summit program includes keynotes, three tracks, workshops, evening party on Friday and Meegathon competition. On Saturday we have Finhack (http://www.finhack.org) annual conference on the second floor.

=== Confirmed Speakers ===
Topics will be set later, in February - March.
* Carsten Munk (keynote) - http://meego.com/users/stskeeps
* Valtteri Halla (keynote) - http://fi.linkedin.com/in/valhalla
* Thiago Macieira (keynote) - http://conference2010.meego.com/people/thiago
* David Greaves - http://conference2010.meego.com/people/lbt
* Dave Neary - http://conference2010.meego.com/people/dneary
* Ville Ilvonen - http://conference2010.meego.com/people/vilvo

=== Tracks ===
In every organization, there are people who just have the knack for getting the most out of certain software and tools. These tracks are where those people shine -- it is the place to show off the newest tools, share creative uses for old favorites, and of course pass on hacks, tips and tricks. Sessions may include demonstrations, pilot projects, examples, techniques, and lessons learned.

# '''Core & Future''' - Apps and possibilities with latest tools (Fri - Sat)
# '''Hacks & Tricks''' - HW inventions, unconventional experiments (Fri - Sat)
# '''Biz Buzz''' - MeeGo Ecosystem and Open Source (Fri)

=== Hackshops ===
Also known as lame Workshops. Participating to Hackshops requires sufficient amount of hack attitude and enthusiasm. We have some facilities (small meeting rooms) for hackshops. If you get an idea about what to teach/show to others (preferably hands-on stuff), book yourself a hackshop space and let the organizers know about it by dropping at the information desk! Your hackshop will be announced in twitter and on the venue screens. If you already know a topic, put it below.

'''Ideas for Workshop.'''

Add your ideas for workshops below. Also add your name if willing to run the workshop.
* ...

=== Meegathon ===
Meegathon is a hacker type of competition, much like a hack-a-thon. The following competition takes place between Fri 12:00am and Sat 12:00am. All teams demonstrate their results Saturday to all event participants. Best inventions and innovations are rewarded. Competition includes two categories:
* Hardcore (HW & SW)
* Quick & Dirty (SW only)

''' Hardcore '''
* the end-product must include and use MeeGo OS (1.1 or above) as one of the main components.
* the end-product HW must be self-made (may include manufactured circuits, wires, connectors, etc)
* keep the size in reasonable limits, eg no monster cars or full scale helicopters.
* all pyrotechnics and acid based solutions are forbidden!
* the agenda of your project is not limited in anyway (except the above).

''' Quick & Dirty '''
* must include only software.
* the end-product must include and use MeeGo OS (1.1 or above) as one of the main components.
* hardware available: web cameras, wires,...
* the agenda for the software is given in the beginning of Meegathon and is the same for all.
* software produced must run on one of the following hardware:
** Nokia N900
** Lenovo Ideapad S10-3t Tablet or similar
** The list of devices will be updated later.

All teams have a dedicated space where to build stuff in the second floor. The space is a big hall, which is divided into smaller areas.

''' Team rules '''
* max 5 persons
* no limitations to member origin (eg from corporate, hackerspaces, LUG's, etc) If the team is sponsored by corporation or includes only corporation employees, it MUST be stated in project description.
*

=== Party ===
* name of the party?

=== Session types ===

'''Hands-on'''

Hands-on sessions are a central focus of the summit and attendees will have the opportunity to learn a wide range of new skills and software in these special sessions. Seating for hands-on sessions is limited and admittance requires pre-registration and a ticket. Sessions are 75(?) minute presentations in a dedicated room. Topics for a session should include any of the previously mentioned Session Tracks.

== Sponsoring ==
Sponsoring opportunities and packages

'''Sponsors:'''

* Ixonos (Main Sponsor)
* Tieto

== How to contribute? ==
Interested in helping? Great! Contributing is easy and you can give as little or as much time as you want.

Here are just a few ways you can get started:
* Check the TODO list below to find something that needs to be done.
* Join discussion at our IRC channel: #meego-fi (irc.freenode.org) and ask what you can do. If you don't have a IRC client, you can access the channel from this free service: http://webchat.freenode.net/
* Join our mailing list (add here)

Here are some of the volunteer opportunities:
* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - 14th Apr.
* Conference Cleanup - 16th Apr
* Speaker Assistants
* Hacking Session Helpers

Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:'''

* Juha [http://twitter.com/#!/riussi @Riussi] Ristolainen
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Carol [http://twitter.com/cybette @cybette] Chen
* Ville [http://identi.ca/jykae @jykae] Jyrkkä

== TODO ==
List of tasks etc that needs to be done by organizers or volunteers. Add your name after a task if you want to do it.
* Define and collect software package (collected about a week before Summit) given for every attendee in a USB stick. 300 pcs. Cuts back the need to download all software from the net. USB-sticks will be provided by New Factory.
* Marketing material: t-shirts, stickers, flyers....
*