From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: want to verify proper use of run-postinsts, if i may
Date: Fri, 29 Jul 2016 12:58:34 +0100 [thread overview]
Message-ID: <1469793514.9142.61.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1607290750390.23975@localhost.localdomain>
On Fri, 2016-07-29 at 07:54 -0400, Robert P. J. Day wrote:
> On Fri, 29 Jul 2016, Richard Purdie wrote:
>
> > On Fri, 2016-07-29 at 07:43 -0400, Robert P. J. Day wrote:
> > > On Fri, 29 Jul 2016, Robert P. J. Day wrote:
> > >
> > > ... snip ...
> > >
> > > > am i missing anything? i'm assuming i'd use a .bbappend recipe
> > > > to
> > > > add the script names to SRC_URI, then define
> > > > "do_install_append()"
> > > > to manually copy them over, or is there a proper way to do that
> > > > i'm
> > > > not seeing?
> > >
> > > never mind, just found an example that confirmed just what i
> > > suspected:
> > >
> > > https://github.com/meta-debian/meta-debian/blob/daisy/recipes-deb
> > > ian/
> > > run-postinsts/run-postinsts_1.0.bbappend
> >
> > Personally, I wouldn't take meta-debian as a good example of
> > anything, that layer is doing some things which I'd find
> > questionable. Obviously they are free to do so though.
> >
> > Most of the time the package manager sets up things to run under
> > run
> > -postinsts as needed. Yes, you can do this automatically, but why
> > not just write a postinstall for your package and defer it to first
> > boot if that is what you need?
>
> it's not just package post stuff here, i'm looking at run-postinsts
> to do a *lot* of subsequent setup of the target system -- effectively
> downloading and installing the entire proprietary application.
>
> yes, i realize i could just make that app part of the initial
> image,
> but there are reasons for this. so i'm assuming just manually
> installing and running some scripts via run-postinsts is the way to
> go.
Note that if there aren't files there to run, I think run-postinsts
disables itself from subsequent boots so it really is designed for "one
-shot" use. It may not run at all if there is nothing to run.
Cheers,
Richard
next prev parent reply other threads:[~2016-07-29 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 11:34 want to verify proper use of run-postinsts, if i may Robert P. J. Day
2016-07-29 11:43 ` Robert P. J. Day
2016-07-29 11:48 ` Richard Purdie
2016-07-29 11:54 ` Robert P. J. Day
2016-07-29 11:58 ` Richard Purdie [this message]
2016-07-29 12:03 ` Robert P. J. Day
2016-08-01 16:14 ` Burton, Ross
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=1469793514.9142.61.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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