daily-feed vs. SRCREV
Rod Whitby
rod at whitby.id.au
Wed Jul 30 02:23:04 CEST 2008
Joachim Breitner wrote:
> Why does the build host at
> http://buildhost.openmoko.org/daily-feed/armv4t/
> not contain packages from webkit r35062 when this is, according to
> http://git.openmoko.org/?p=openmoko.git;a=blobdiff;f=conf/distro/include/sane-srcrevs.inc;h=05538c244f6397f1a272deabbb7c6c199d79ca44;hp=fcae48f974c63e8d78b04c95707f6f64efeac9ea;hb=c9f28bb1f745938015ca53100218e33bde75f75e;hpb=92fb2948301b69c81c915cbafb937dcc42115030
> the current version?
My understanding (which could easily be out of date) is that the
buildhost builds with moko-autorev.inc (which negates the impact of
sane-srcrevs.inc for a set of openmoko-related packages).
Why they do that, which is effectively pushing completely untested
builds onto thousands of end-users, is beyond my understanding.
Openmoko should have a single set of known good versions (documented in
sane-srcrevs.inc) which are distributed to the public through the
buildhost daily builds. Individual openmoko developers working on a
certain package should let the version for their specific package float
while they are testing the new version, but as soon as they are
confident the new version works, then they should update sane-srcrevs so
that the public gets the newly tested version.
-- Rod
More information about the devel
mailing list