Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches,
	about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] rootfs generation: export two new variables to postinst scriptlets
Date: Wed, 05 Dec 2012 15:30:41 +0000	[thread overview]
Message-ID: <1354721441.25268.117.camel@ted> (raw)
In-Reply-To: <CAP9ODKpZjFRF3FYWzf3BMWYuEBzbb1YrXyG3zpj5OJVdkrNEYw@mail.gmail.com>

On Tue, 2012-12-04 at 13:07 -0200, Otavio Salvador wrote:
> 
> 
> 
> On Tue, Dec 4, 2012 at 11:59 AM, Laurentiu Palcu
> <laurentiu.palcu@intel.com> wrote:
>         In order for the postinst scriptlets to be able to run once we
>         need to
>         export the location of the intercept scripts and also the
>         location of
>         native sysrootfs. The gdk-pixbuf binaries will need the latter
>         because
>         in order to generate the loaders.cache it will need to scan
>         some shared
>         libraries that must be native. Even though the output is a
>         text file.
>         
>         Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
>         ---
>          meta/classes/package_rpm.bbclass |    2 ++
>          meta/classes/rootfs_deb.bbclass  |    2 ++
>          meta/classes/rootfs_ipk.bbclass  |    2 ++
>          3 files changed, 6 insertions(+)
>         
>         diff --git a/meta/classes/package_rpm.bbclass
>         b/meta/classes/package_rpm.bbclass
>         index 1ff92ce..c7ac07a 100644
>         --- a/meta/classes/package_rpm.bbclass
>         +++ b/meta/classes/package_rpm.bbclass
>         @@ -475,6 +475,8 @@ export D="${target_rootfs}"
>          export OFFLINE_ROOT="\$D"
>          export IPKG_OFFLINE_ROOT="\$D"
>          export OPKG_OFFLINE_ROOT="\$D"
>         +export INTERCEPT_DIR="${WORKDIR}/intercept_scripts"
>         +export NATIVE_ROOT=${STAGING_DIR_NATIVE}
> 
> 
> The NATIVE_ROOT seems a duplication, I'd prefer you to use
> STAGING_DIR_NATIVE in code as this is a known variable name and makes
> it easy to understand.
 
I'm going to disagree on that, I think this does make sense in the
context of the functions we're changing here.

On the other hand I'd love to simplify the whole *OFFLINE_ROOT mess but
that is for a different patch...

Cheers,

Richard





  reply	other threads:[~2012-12-05 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 13:59 [PATCH 0/5] Postinstall improvements Laurentiu Palcu
2012-12-04 13:59 ` [PATCH 1/5] image.bbclass: run postinst scripts once, at rootfs time Laurentiu Palcu
2012-12-04 14:10   ` Otavio Salvador
2012-12-04 13:59 ` [PATCH 2/5] rootfs generation: export two new variables to postinst scriptlets Laurentiu Palcu
2012-12-04 15:07   ` Otavio Salvador
2012-12-05 15:30     ` Richard Purdie [this message]
2012-12-04 13:59 ` [PATCH 3/5] gtk-icon-cache: run the icon generation at rootfs time Laurentiu Palcu
2012-12-04 13:59 ` [PATCH 4/5] gdk-pixbuf: generate the pixbuf loader's cache ar " Laurentiu Palcu
2012-12-04 14:34   ` Burton, Ross
2012-12-05  9:28     ` Laurentiu Palcu
2012-12-14 14:24       ` Burton, Ross
2012-12-04 13:59 ` [PATCH 5/5] gconf.bbclass: run postinstalls at " Laurentiu Palcu

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=1354721441.25268.117.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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