Skip to contentSkip to conversation

Packaged-staging v2

DISCUSSION Koen Kooi 1 participant 1 message Jul 29, 2007

lore
Share & tools
lore

Koen Kooi

author
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Last year we had a google SoC to implement packaged-staging. The resulting .bbclass worked for the small subset of recipes in the branch, but not for .dev. After a while we realised that multithreaded bitbake kills the current implementation.

During last OEDEM, FOSDEM and GUADEC Richard and I discussed the problems at hand:

a) the 'extra' data in staging (shlibs, pkgdata, etc) needs to get packaged as well
b) fake stamps need to get injected
c) recipes should have a way to mark which entries from PACKAGES are needed when there are heavily granulated
d) staging needs to be locked during packaging and population
e) cross/ needs to get packaged as well

Preferably package format agnostic :)

Poky recently gained support building an sdk toolchain and using that as the OE cross toolchain later on ("Poor mans packaged-staging"). We can solve e) using that.

I'd like to ask for some advice and input on how to solve the problems in a clean way.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGrFbQMkyGM64RGpERAtUmAJwN1dBqoRac1FH+bKnn6Ul2UqCj8gCfVEDL p7qwFWZaGgMB7k1otTLXSRk=
=6RDJ
-----END PGP SIGNATURE-----