[RFC] OM dev policy related to OE
john_lee at openmoko.com
Thu Jan 3 12:55:48 CET 2008
Please refer to
We got some problems about moko-autorev.inc (using the latest version
in image and ipkgs) because people will commit code that depends on
the upstream OE which might not in sync with what's on OM mtn.
Including moko-autorev.inc often introduces new revs that depend on
the later version of OE. These problems will be fixed on next sync
and personnally I won't fix them between syncs.
If we want to use OM mtn for development, the policy should be clear
that ALL OM related packages cannot commit code that depends on
upstream OE instead of OM mtn. There's no way we could maintain a
stable daily build if we keep changing the outside dependency.
More information about the openmoko-devel