On Tue, 2012-12-04 at 13:49 -0600, Mark Hatle wrote:
> From: Paul Eggleton <[email protected]>
> 
> Use Smart to construct the root filesystem for images and the contents
> of SDKs rather than the custom scripts around rpm we had previously.
> This ensures the result when producing an updated image will be the
> same as upgrading to the same package versions from an older image on
> the target, as well as allowing us to remove a substantial amount of
> code making the rpm classes much easier to follow.
> 
> Some bugfixes from Bogdan Marinescu <[email protected]>.
> SDK implementation and testing as well as a number of bugfixes from
> Mark Hatle <[email protected]>.
> 
> Signed-off-by: Paul Eggleton <[email protected]>
> Signed-off-by: Mark Hatle <[email protected]>
> ---
>  meta/classes/package_rpm.bbclass      |  533 
> ++++++---------------------------
>  meta/classes/populate_sdk_rpm.bbclass |   48 +---
>  meta/classes/rootfs_rpm.bbclass       |   31 +-
>  3 files changed, 117 insertions(+), 495 deletions(-)
> 
> diff --git a/meta/classes/package_rpm.bbclass 
> b/meta/classes/package_rpm.bbclass
> index 200a941..aa5b156 100644
> --- a/meta/classes/package_rpm.bbclass
> +++ b/meta/classes/package_rpm.bbclass
> @@ -8,6 +8,8 @@ RPMBUILD="rpmbuild"
>  PKGWRITEDIRRPM = "${WORKDIR}/deploy-rpms"
>  PKGWRITEDIRSRPM = "${DEPLOY_DIR}/sources/deploy-srpm"
>  
> +EXTRANATIVEPATH += "python-native"
> +

Er, no!

Why do we need to do this? We now need python-native at package
generation time? Why?

There is no dependency for that and this would totally kill build
performance if we did add it.

Cheers,

Richard


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to