From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: why is "run-postinsts" considered a "development" recipe?
Date: Tue, 26 Jul 2016 10:03:45 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1607261001570.14189@localhost.localdomain> (raw)
for the first time, i want to use run-postinsts to run some initial
system setup, so i'm assuming i need to add that recipe to my image
and the associated files, but i'm curious as to why run-postinsts
lives under recipes-devtools. it doesn't strike me as a development
tool, so what's the reasoning there? thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2016-07-26 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:03 Robert P. J. Day [this message]
2016-07-26 14:07 ` why is "run-postinsts" considered a "development" recipe? Burton, Ross
2016-07-26 14:19 ` Robert P. J. Day
2016-07-26 14:23 ` Burton, Ross
2016-07-26 14:27 ` Robert P. J. Day
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=alpine.LFD.2.20.1607261001570.14189@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox