Usage of monotone.openmoko.org

[John Lee]

On Thu, Jan 03, 2008 at 03:45:44PM +0000, Thomas Wood wrote:
> Hi,
> 
> Further to the discussion on bug 1152 [1], I would like to seek some
> clarification on the use cases for monotone.openmoko.org.
> 
> The problem hilighted in bug 1152 is that monotone.openmoko.org is not
> currently buildable if you are using the autorev feature of bitbake.
> This is necessary for OpenMoko developers to make sure the OpenMoko
> components are built from the very latest revisions in SVN. Currently,
> OpenMoko SVN depends on features not available in monotone.openmoko.org.

Hi Thomas,

Cross post my mail on openmoko-devel:

Date: Thu, 3 Jan 2008 19:55:48 +0800
From: John Lee <john_lee at openmoko.com>
To: a list for all members of the openmoko software team
        <software-team at lists.internal.openmoko.org>, Development of third party
        programs for OpenMoko <openmoko-devel at lists.openmoko.org>
Subject: [RFC] OM dev policy related to OE

Hi,

Please refer to

http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1152

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.

Quote myself:

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.

Your comments?

> Secondly, I will soon have a new problem. I am currently working on
> integrating PackageKit into an OpenMoko build. This will require updates
> in OpenMoko package versions as it will require dbus >= 1.1.1. I have
> already got dbus 1.1.1 added to OpenEmbedded but I am unsure what the
> expected procedure is with regards to monotone.openmoko.org. Should I
> integrate PackageKit into OpenEmbedded first or into
> monotone.openmoko.org first?

This is rather a grey area for me.  If dbus >= 1.1.1 is a requirement
that you cannot integrate PackageKit without it, I will lean toward
commit to OM first, make sure the latest version builds, then merge
upstream.  Commit to OE really seems reasonable but that will break
daily builds and I really hope moko-autorev.inc + OM mtn works.

Regards,
John