From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
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:48:33 +0100 [thread overview]
Message-ID: <1469792913.9142.56.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1607290735180.23808@localhost.localdomain>
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-debian/
> 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?
Cheers,
Richard
next prev parent reply other threads:[~2016-07-29 11:48 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 [this message]
2016-07-29 11:54 ` Robert P. J. Day
2016-07-29 11:58 ` Richard Purdie
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=1469792913.9142.56.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 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.