Usage of monotone.openmoko.org
k.kooi at student.utwente.nl
Thu Jan 3 17:32:41 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
Thomas Wood schreef:
> Further to the discussion on bug 1152 , 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.
Right, that means you are mixing something that is described with
'frozen' with something that is described with 'bleeding edge'. I don't
see how anyone expects that to work.
> 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.
If mtn.om.org really wants to be what it claims ('frozen', 'stable',
'always buildable' etc) it shouldn't be using autorev.
> 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?
You mean creating an ipkg backend for PackageKit?
> Finally, I think the big questions is whether monotone.openmoko.org is
> specifically for third party developers, or should core OpenMoko
> developers be using it as well.
>  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1152
koen at dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi at student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----
More information about the distro-devel