[oe] openembedded / dpkg-buildpackage hybrid
Esben Haabendal
esbenhaabendal at gmail.com
Wed Nov 24 19:43:10 UTC 2010
On Wed, Nov 24, 2010 at 3:19 PM, Chris Larson <clarson at kergoth.com> wrote:
> Have you taken a look at the work Richard Purdie has done on bitbake
> for Poky/Yocto?
Yes, I am aware of the work done for Poky. But with regards to staging,
I just want to go the direct way and have package-based, per-recipe
staging now. I am aware that this would be a huge effort to undertake
for entire OpenEmbedded, but I don't have to do that for now.
> It isn't refactoring the way you've done, but it does rework how
> packaged staging is used.
I understand that the idea is to take micro-steps from the current
situation towards the desired solution, but I simply find both the
Poky/Yocto sstate and the current OpenEmbedded staging situation both to
error-prone and complicated. KISS rules here ;-)
> It implements per-task metadata checksumming (based upon my oe
> signatures code) and task level output archiving for populate_sysroot,
> to be used to short-circuit its build in subsequent runs.
> Conceptually its an interesting tactic, and I think metadata
> checksumming is going to be critical going forward, to improving our
> build reproducibility.
I am also in the process of adding metadata and source checksumming.
The checksumming of dependencies of-course ends up being rather
different based on the different approach to build dependencies. For
now, I have metadata and dependency checksumming for all tasks, and hope
to soon add package-based dependency checksumming, which will enable
some interesting effects with regards to re-use of prebuilt packages.
But definitely, metadata checksumming is on the critical path forwards
if we want to improve build reproducibility. But so is per-recipe
staging.
/Esben
More information about the Openembedded-devel
mailing list