This thread is continuum of my "Rebasing Fremantle on top of Debian 6" [http://talk.maemo.org/showthread.php?t=89416]

I have reached one milestone and now I'm looking for testers and starting discussion how to utilize all of this.

Here are packages:
http://www.cs.helsinki.fi/u/rantalai.../wheezy/repo2/
http://www.cs.helsinki.fi/u/rantalai.../wheezy/waemo/

(there are also older repository: http://www.cs.helsinki.fi/u/rantalai...5/wheezy/repo/
and here is squeeze packages: http://cc.oulu.fi/~rantalai/maemo5/squeeze/repo/ )

--------------
Motivation:
*Claim1: new version of package is better than old (todo: proof for every package)
*Compiling new code will be easier if libraries and tools are newer.
*It would be possible to install packages straight from Wheezy-armel repository.
--------------
Goal:
(Term package refers to 'binary'-package, which means installable package, not source package, which produce one or more (even tens) binary-packages).

Just installed/flashed Maemo5 has 1745 packages (http://wiki.maemo.org/User:Aapo/Waemo/DefaultPackages), 355 of them are closed (http://wiki.maemo.org/Fremantle_closed_packages) and not scope of this.

Most open packages are made by Nokia and there are no newer Debian versions (but there could be newer upstream or Meego code, but it is not scope of this.)

There are 181 Fremantle packages which are also in Wheezy ( http://wiki.maemo.org/User:Aapo/Waemo/Upgradeable ).
(There are also 26 Fremantle packages in Squeeze but not in Wheezy. These might or might not be in scope of this).


First task for every package is to get it compiled (and its build dependencies). Then installed (and its dependencies) without bricking the device. After that starting to look if it breaks some functionality or if it is causing any side effects (CPU, memory, disk space).

---------
Goal2:
Recompile ~1200 Nokia packages using Wheezy toolchain. (This comes very close to the CSSU and thumb-recompiling.)

This step might be out of this scope, because many package works without recompiling (thanks to good backward compatibility). There are at least one counter example: hildon-application-manager must be compiled against newer libapt (which is now done and it is not bricking the device).

---------
Status on 1 Nov 2013: http://wiki.maemo.org/User:Aapo/Waemo/Status

These packages can be installed without immediate brick: http://www.cs.helsinki.fi/u/rantalai...mo_install.txt
(Note: I have installed top part of the list more often than end of the list (so they are 'more tested'))

You can download script to the /home/user before flashing. After flashing rootfs you need either ssh-server or rootsh installed via Application manager and then just run the script, it will take ~30minutes to run.

Next steps (maybe in parallel):
* Testers: upgrade your device and report what breaks (for sure something breaks, prepare for reflash!)
* Maemo developers: How to use this all (or part) to improve Fremantle?
* How to upgrade hard packages? (hal, udev, gtk, gstreamer)