Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Luo Zhenhua-B19537 <B19537@freescale.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe-core v2] rpm: split out run-postinsts
Date: Mon, 25 Mar 2013 10:44:01 +0000	[thread overview]
Message-ID: <1364208241.3097.38.camel@ted> (raw)
In-Reply-To: <CA452391058F6D4E9715FB2C29D9312A01487E80@039-SN2MPN1-022.039d.mgd.msft.net>

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




      reply	other threads:[~2013-03-25 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21  2:05 [oe-core v2] rpm: split out run-postinsts Zhenhua Luo
2013-03-22 16:29 ` Richard Purdie
2013-03-22 17:04   ` Mark Hatle
2013-03-25 10:38     ` Luo Zhenhua-B19537
2013-03-25 10:44       ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1364208241.3097.38.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B19537@freescale.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox