On Mon, 2013-03-25 at 10:38 +0000, Luo Zhenhua-B19537 wrote:
> > > Don't we need to depend on this package somewhere so that it gets
> > > installed?
> >
> > I think it should be required from the rootfs_rpm.bbclass in some way.
> [Luo Zhenhua-B19537] Is following the right way to include the rpm-postinsts
> into rootfs or any better idea? Below patch is verified to be working.
>
> --- a/meta/classes/rootfs_rpm.bbclass
> +++ b/meta/classes/rootfs_rpm.bbclass
> @@ -35,6 +35,8 @@ opkglibdir = "${localstatedir}/lib/opkg"
> RPMOPTS="--dbpath ${rpmlibdir}"
> RPM="rpm ${RPMOPTS}"
>
> +IMAGE_INSTALL += "rpm-postinsts"
> +
> # RPM doesn't work with multiple rootfs generation at once due to collisions
> in the use of files
> # in ${DEPLOY_DIR_RPM}. This can be removed if package_update_index_rpm can
> be called concurrently
> do_rootfs[lockfiles] += "${DEPLOY_DIR_RPM}/rpm.lock"
Looking at rootfs_ipk:
ROOTFS_PKGMANAGE = "opkg opkg-collateral ${EXTRAOPKGCONFIG}"
ROOTFS_PKGMANAGE_BOOTSTRAP = "run-postinsts"
seems to be a pretty good setup to copy, particularly given the rpm
counterpart:
# Postinstalls on device are handled within this class at present
ROOTFS_PKGMANAGE_BOOTSTRAP = ""
which is no longer true.
Cheers,
Richard
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
