Mer
(→Iteration 2: Mer Alpha)
Line 70: Line 70:
'''Mer''': Provide a experimental system for Maemo community use, as a playground to try out new technologies and ideas on. Give community a voice in system architecture and continued development of the Maemo platform post Fremantle. Give the community ability to give documented, researched input to the development process of Maemo. Mer should be cross-platform, both for i386, armel, and not rely on running on specific devices.
'''Mer''': Provide a experimental system for Maemo community use, as a playground to try out new technologies and ideas on. Give community a voice in system architecture and continued development of the Maemo platform post Fremantle. Give the community ability to give documented, researched input to the development process of Maemo. Mer should be cross-platform, both for i386, armel, and not rely on running on specific devices.
-
Upstream distribution:
+
'''Upstream distribution:'''
Ubuntu 'Jaunty' for ARM and i386. Experiment with VFP/optimized versions (use of hwcap) for libraries that would benefit from it.
Ubuntu 'Jaunty' for ARM and i386. Experiment with VFP/optimized versions (use of hwcap) for libraries that would benefit from it.
Maemo trunk
Maemo trunk
-
Development process:  
+
'''Development process:'''
Use of launchpad.net (http://launchpad.net/m-r). Everything must be done in bzr branches and published in the m-r project on launchpad. Use of builders (http://merbuilder.jaiku.com), which only accepts bzr branches and source packages. Packages must compile in both i386 and armel ideally.
Use of launchpad.net (http://launchpad.net/m-r). Everything must be done in bzr branches and published in the m-r project on launchpad. Use of builders (http://merbuilder.jaiku.com), which only accepts bzr branches and source packages. Packages must compile in both i386 and armel ideally.
Microdocumentation is still done in jaiku, http://jaiku.com/channel/reconstructedPOC
Microdocumentation is still done in jaiku, http://jaiku.com/channel/reconstructedPOC

Revision as of 23:12, 24 November 2008

Contents

Organizational

"Mer" is an experimental project, where an attempt of "reconstructing" the Maemo platform is done, based on the proposal on http://wiki.maemo.org/Maemo_Reconstructed. Mer means ocean in french, "more" in danish, etc..

Launchpad page

http://launchpad.net/m-r

Platforms targeted

  • jaunty-armel
  • jaunty-i386

Repositories and branches

Repositories at http://trac.tspre.org/mer/<arch>

  • alpha:

Branching from Maemo packages

  • get bzr-svn, bzr
  • bzr branch <svn-url>
  • bzr push bzr+ssh://username@bazaar.launchpad.net/~username/m-r/<package name>

Builder system

Status: http://merbuilder.jaiku.com

Requests: http://jaiku.com/channel/merbuilder

Authorized users (identified by their login) can ask builder by sending <platform regexp> <bzr branch url> to start building on archs matching the platform regexp. For example, jaunty-* lp:~carsten-munk/m-r/glib

Build system

  • dell1-qemu-arm: pentium4 handling jaunty-armel on a qemu-system-arm. Location: Århus, DK
  • dell1: pentium4 handling jaunty-i386. Location: Århus, DK

System base consists of (with dependancies)

  • Minbase from 'platform'
  • + wget, apt-utils, udev, bash, dash, module-init-tools, findutils, gzip, hostname, ifupdown, net-tools, procps, sed, tar, coreutils, grep, mount, bsdutils, debianutils, vim-tiny, mawk, mktemp, sysvutils, iputils-ping, psmisc, time, login, passwd, udhcpc, wide-dhcpv6-client
  • clinkc0, dbus, xorg-xserver, bluez-utils, dosfstools gconf2 hal libgupnp-1.0-0 libsmbclient mtools pulseaudio samba-common

Image goals to build using Mer

  • N8x0 platform QEMU image
  • Example "Vendor" image, N8x0 platform with HW support (wifi, GPS, Adobe Flash, gstreamer codecs), scripts for building
  • x86 images (tar.gz)
  • Pandora images

Roadmap =

Iteration 1 (done)

Idea: Build as much of Maemo trunk we can, adapt to Ubuntu, chaos coding, microdocument through Jaiku (http://jaiku.com/channel/reconstructedPOC), and make it work and run. Name was M-R PoC.

Results were 123mb flash for minimal ubuntu base system, hildon on top. Possible to do things like:

A choice was made to restart and do things by the book. We originally based on Mojo Handhelds Ubuntu port to ARM.

Iteration 2: Mer Alpha

Mer: Provide a experimental system for Maemo community use, as a playground to try out new technologies and ideas on. Give community a voice in system architecture and continued development of the Maemo platform post Fremantle. Give the community ability to give documented, researched input to the development process of Maemo. Mer should be cross-platform, both for i386, armel, and not rely on running on specific devices.

Upstream distribution:

Ubuntu 'Jaunty' for ARM and i386. Experiment with VFP/optimized versions (use of hwcap) for libraries that would benefit from it. Maemo trunk

Development process:

Use of launchpad.net (http://launchpad.net/m-r). Everything must be done in bzr branches and published in the m-r project on launchpad. Use of builders (http://merbuilder.jaiku.com), which only accepts bzr branches and source packages. Packages must compile in both i386 and armel ideally.

Microdocumentation is still done in jaiku, http://jaiku.com/channel/reconstructedPOC

Retrieved from "https://wiki.maemo.org/Mer"