Merging openmoko into OE
Koen Kooi
koen at dominion.kabel.utwente.nl
Thu Mar 1 15:58:11 CET 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
A quick inspection shows that openmoko userspace in OE contains more recipes and bugfixes
than the userspace in trunk/oe. This morning I noticed that the gsm panel plugin has been
converted to mb-panel-2, so packaging will need to be adjusted.
Therefore I want to propose to start deprecating trunk/oe next week.
What needs to be done:
* update openocd + deps into OE
* update uboot in OE
* update 2.6.20 in OE
* merge sourcepkg.bbclass
* Do some test builds
(* fix bugs in above builds)
* note down working revision
* delete recipes from svn
That only leaves the decision wether to lock down to the working revision for p0 and p1.
My gut feeling is that p0 doesn't need a locked down revision, since a lot of bugs will
get uncovered and fixed. For p1 I'm not sure what to advice, but p2 will need a snapshot
or branch for sure. Keep in mind that maintaining a branch is almost a full-time job if
you want to do it right.
What are the plans, and how can the community help with carrying those out?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFF5uoDMkyGM64RGpERArmyAJ99iMIqEPSw+O6LBMKTJSTVI6kG9ACdFPSn
HHOwe2Alpui5pU+3JII0pxU=
=dDZf
-----END PGP SIGNATURE-----
More information about the distro-devel
mailing list