[oe] Merging openmoko into OE
koen at dominion.kabel.utwente.nl
Mon Mar 5 11:56:54 CET 2007
-----BEGIN PGP SIGNED MESSAGE-----
Harald Welte schreef:
> On Thu, Mar 01, 2007 at 03:58:11PM +0100, Koen Kooi wrote:
>> What are the plans, and how can the community help with carrying those out?
> Our current agenda is more focussed on "getting things working at all"
> rather than "doing everything correct in the first run". I wish it was
> different, but we're really under a lot of pressure here.
> As far as the buildsystem is addressed, there are some distinct features
> which we're lacking currently. I have hired an experienced python
> hacker to add those things properly to bitbake and then talk to you guys
> about how this code can be merged.
> Our primary requirements, with regard to the build system, are:
> 1) do proper and reliable caching, dependency resolving, and decisions
> on when to build what, while staying in-sync with upstream
> repositories. We're working on somce code that adds methods to the
> fetchers (so far: only svn) to determine the 'last changed date' of
> the upstream repo. Then we create a string as concatentation of all
> source uri repositories, and use that as PR. This gets rid of the
> bogus timestamps and neverending rebuilds of the same source code.
> Also, the tarballs in 'sources' (which get mirrored to
> downloads.openmoko.org/sources) will then contain e.g. the svn
> revision number, not the checkout date.
> This whole logic will be optional, and only be active for
> SRCDATE="now" packages.
> Using this method we can e.g. only rebuild the uboot package if
> either upstream git or our quilt patchset in svn have changed.
> I know this might conflict with where bitbake is heading, or what is
> currently in 1.7.x. We will investigate this later, once we have
> something that fits our needs first. I know this is very
> un-free-software-like, but we really are short of months of time [and
> staff] and have to compromise somewhere.
> 2) run automatized builds on one of our buildhosts, continuously,
> sending reports about build failures directly into bugzilla.
Holger has modified(/rewritten) tinderbox code to do such a thing. It need a recent
bugzilla with xmlrpc turned on.
> 3) find a cleaner way for the deploy/images directory. There need to be
> per-release symlinks so that an automatized flashing tool can always
> assume that the current kernel for one release/snapshot/branch has a
> fixed name (can be symlinks).
Ok, that's not too hard, I recall Richard making a start with that for the zaurus machines.
> Also, the statically linked native
> openocd, dfu-util and sjf2410 binaries need to go to a different
Rod is looking into proper statical linking. We probably need a DEPLOY_DIR_TOOLS or
something where the tools will live.
> 4) find a way how to correctly clean up packages after a build.
> Something like: If I rebuild a kernel uImage, then only the most current
> one is supposed to be in 'images', older ones get moved to 'attic'.
That one is a bit nasty, since people might want to have it all in one dir, and might
freak out when OE moves it away to another dir. I'm not one of those people :)
> 5) find a way how to completely clean up a package, including all
> related download cache, bitbake rule cache, .ipk's and/or 'images'
> that it created
Holger and I discussed something like that for the packaged-staging project, but we didn't
come up with a clean way to present it to the user. That was last year, and I'm sure
others can come up with something.
> 6) find how how we can automatically create a full 'snapshot' from a
> current build-directory, by just using the latest version of every
> kerne/uboot image and .ipk
What kind of snapshot are you talking about? A flashable image, a tarball or the OE
recipes, ... , ... ?
> 7) related: reimplement ipkg backend to use some indexed database. It's
> just too slow
You can make it about twice as fast by doing:
for i in `find . -name Packages` ; do grep -v ^Source: $i|gzip -c9>$i.gz ;gunzip -c
$i.gz>$i ; done
Marcin looked at it briefly, and it seems that using an sqlite3 database will use up the
same size for the list of available packages.
> 8) think about signing binary packages and feeds plus signature
> verification on the device
That'd be nice and can probably implementing within the current control file format.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----
More information about the Openembedded-devel