Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC 2/7] image.bbclass: run postinst scripts once, at rootfs time
Date: Wed, 19 Sep 2012 18:45:23 +0300	[thread overview]
Message-ID: <5059E893.1060300@intel.com> (raw)
In-Reply-To: <CAJTo0LafLwJxBi4eG_CF+iviJbPT4HwtDdkssCAGeOgzv1t2XQ@mail.gmail.com>



On 09/19/2012 06:14 PM, Burton, Ross wrote:
> On 19 September 2012 12:49, Laurentiu Palcu <laurentiu.palcu@intel.com> wrote:
>> +ROOTFS_POSTPROCESS_COMMAND ?= "run_intercept_scriptlets"
> 
> From other examples, it looks like this should be "run_intercept_scriptlets;"
Will do. My bad.

> 
> Also whilst this is a great proof of concept, maybe it should be
> integrated into image.bblcass directly instead of being a postprocess
> hook?  A postprocess hook might expect the postinstall scripts to have
> been ran already, which they would have been if they were not
> intercepted.
I'm a little confused here... Technically, when the postprocess hooks
are executed all the postinstall scripts were already executed. Ideally,
the run-once scripts are created from inside the postinst scriptlets
themselves. So, I don't really understand why using the postprocess hook
isn't safe. Can you please elaborate?

Thanks,
Laurentiu
> 
> Ross
> 



  reply	other threads:[~2012-09-19 15:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 11:49 [RFC 0/7] Postinstall improvements Laurentiu Palcu
2012-09-19 11:49 ` [RFC 1/7] gtk+: enable gtk+-native Laurentiu Palcu
2012-09-19 11:49 ` [RFC 2/7] image.bbclass: run postinst scripts once, at rootfs time Laurentiu Palcu
2012-09-19 15:14   ` Burton, Ross
2012-09-19 15:45     ` Laurentiu Palcu [this message]
2012-09-19 15:50       ` Burton, Ross
2012-09-19 17:12         ` Laurentiu Palcu
2012-09-20 12:25   ` Richard Purdie
2012-09-19 11:49 ` [RFC 3/7] rootfs generation: export two new variables to postinst scriptlets Laurentiu Palcu
2012-09-19 11:49 ` [RFC 4/7] gtk-icon-cache: run the icon generation at rootfs time Laurentiu Palcu
2012-09-19 13:28   ` Khem Raj
2012-09-19 13:38     ` Burton, Ross
2012-09-19 15:26       ` Laurentiu Palcu
2012-09-19 11:49 ` [RFC 5/7] gdk-pixbuf: generate the pixbuf loader's cache ar " Laurentiu Palcu
2012-09-19 13:30   ` Khem Raj
2012-09-19 15:29     ` Laurentiu Palcu
2012-09-19 11:49 ` [RFC 6/7] sato-icon-theme: make use of the gtk-icon-cache postinst scriptlet Laurentiu Palcu
2012-09-19 13:36   ` Burton, Ross
2012-09-19 15:30     ` Laurentiu Palcu
2012-09-19 11:49 ` [RFC 7/7] postinst changes: bump PR to all recipes inheriting gnome and gtk-icon-cache Laurentiu Palcu
     [not found] ` <CALbNGRTCyvfZFYHx6bKV8oVDJWH3X0tj1DHSJm9CkvT4xY2f7A@mail.gmail.com>
     [not found]   ` <5059E5C3.2080603@intel.com>
2012-09-20 15:38     ` [RFC 0/7] Postinstall improvements Andreas Müller
2012-09-20 16:12       ` Andreas Müller
2012-09-20 18:15         ` Laurentiu Palcu
2012-09-20 20:54           ` Martin Jansa
2012-09-26  7:09         ` Laurentiu Palcu
2012-09-26  7:41           ` Andreas Müller
2012-10-03 23:37             ` Andreas Müller
2012-10-04 19:16               ` Andreas Müller
2012-10-05  6:39                 ` Laurentiu Palcu
2012-10-05 20:43                   ` Andreas Müller

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=5059E893.1060300@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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