All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick <kpa_info@yahoo.fr>
Cc: poky@yoctoproject.org
Subject: Re: Running script after installation (postinst)
Date: Thu, 14 Jun 2012 15:40:11 +0100	[thread overview]
Message-ID: <1339684811.24333.88.camel@ted> (raw)
In-Reply-To: <4FD9E759.8010208@yahoo.fr>

On Thu, 2012-06-14 at 15:30 +0200, Patrick wrote:
> On 06/13/2012 05:22 PM, Patrick wrote:
> > On 06/13/2012 04:38 PM, Patrick wrote:
> >> On 06/13/2012 10:08 AM, Richard Purdie wrote:
> >>> You would need to add the dependency in and then it sounds like you're
> >>> probably using rpm and it doesn't want to honour the dependency for some
> >>> reason. You could add a rootfs post process command to add in what you
> >>> need which would guarantee all the files are present first...
> >>
> >> That's a good idea ! What would be the correct function name ? Something
> >> like do_rootfs_append() ?
> >> In this case do we have to prefix all the path with ${IMAGE_ROOTFS} ?
> >>
> >> Patrick
> >
> > I reply myself:
> > as suggested above, using do_rootfs_append() and ${IMAGE_ROOTFS} it
> > works nicely !
> >
> 
> Argh, in fact it doesn't work. The script is executed against right 
> files but *after* packaging everything into a single image...
> The script should be executed just before packaging of the image.
> 
> Any idea how to do that ?

ROOTFS_POSTPROCESS_COMMAND is probably what you're looking for.

Cheers,

Richard





  parent reply	other threads:[~2012-06-14 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 14:35 Running script after installation (postinst) Patrick
2012-06-12 14:47 ` Richard Purdie
2012-06-13  7:18   ` Patrick
2012-06-13  8:08     ` Richard Purdie
     [not found]       ` <4FD8A5F5.4080001@yahoo.fr>
2012-06-13 15:22         ` Patrick
2012-06-14 13:30           ` Patrick
2012-06-14 14:24             ` Patrick
2012-06-14 14:40             ` Richard Purdie [this message]
2012-06-12 14:49 ` Tomas Frydrych

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=1339684811.24333.88.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=kpa_info@yahoo.fr \
    --cc=poky@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.