All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donal Morrissey <donal.morrissey@gmail.com>
To: ross.burton@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: non-existent task do_package_write_ipk
Date: Fri, 9 Nov 2018 15:44:54 +0000	[thread overview]
Message-ID: <CABj1EzEP1Mg5d_cCcsKj68qkwbLYZw2YiLCfE6wV2LTFg3JqKQ@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0La2K+VqcE5WNAbyNsnFkiFazfKcQ5YZ6peTgK2W+=p0XQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

Hi Ross,
I had to use IMAGE_PREPROCESS_COMMAND in my own image recipe, the execution
order of the ROOTFS_POSTPROCESS_COMMAND commands didn't work for me.
Thanks for your help.
Donal

On Fri, 9 Nov 2018 at 14:53, Burton, Ross <ross.burton@intel.com> wrote:

> On Fri, 9 Nov 2018 at 14:48, Donal Morrissey <donal.morrissey@gmail.com>
> wrote:
> > Thank you for your help. My build is using a layer which is generating a
> file in a ROOTFS_POSTPROCESS_COMMAND command. I would like to modify this
> file as part of the yocto build, but I'd prefer not to modify/fork this
> layer as it is from a vender.
> >
> > I'm creating my own layer, which will modify the file created in the
> vender layer's ROOTFS_POSTPROCESS_COMMAND command. If I use pkg_postinst,
> then the file will not have been created when pkg_postinst is called,
> because (as far as i understand) the ROOTFS_POSTPROCESS_COMMAND commands
> will only be executed after all packages have been installed on the root
> filesystem image.
>
> You'll have to set your own ROOTFS_POSTPROCESS_COMMAND in your image
> recipe.
>
> Ross
>

[-- Attachment #2: Type: text/html, Size: 1502 bytes --]

      reply	other threads:[~2018-11-09 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09 11:34 non-existent task do_package_write_ipk Donal Morrissey
2018-11-09 12:12 ` Burton, Ross
2018-11-09 14:48   ` Donal Morrissey
2018-11-09 14:53     ` Burton, Ross
2018-11-09 15:44       ` Donal Morrissey [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=CABj1EzEP1Mg5d_cCcsKj68qkwbLYZw2YiLCfE6wV2LTFg3JqKQ@mail.gmail.com \
    --to=donal.morrissey@gmail.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.