Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: why is "run-postinsts" considered a "development" recipe?
Date: Tue, 26 Jul 2016 10:19:04 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1607261016100.14495@localhost.localdomain> (raw)
In-Reply-To: <CAJTo0LZZ_1V_68Pya9EUNT6imRVONTkrMzejFAGG9A8f3GYfTQ@mail.gmail.com>

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

On Tue, 26 Jul 2016, Burton, Ross wrote:

>
> On 26 July 2016 at 15:03, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>         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.
>
> For no reason reason other than it's intimately tied to
> dpkg/opkg/rpm, which are also in devtools.

  i'm good with that, and one more (potentially idiotic) question
about run-postinsts. i note in the OE recipe file that it inherits
"update-rc.d", but i'm not sure why.

  AIUI (and i could be totally off-base here), i thought systemd
needed update-rc.d only for backward compatibility for sysvinit-style
services, is that right?

  so while run-postinsts is free to inherit update-rc.d, does that
have any value if one is not using any sysvinit-driven services? or am
i misunderstanding the fundamental functionality of update-rc.d?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2016-07-26 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 14:03 why is "run-postinsts" considered a "development" recipe? Robert P. J. Day
2016-07-26 14:07 ` Burton, Ross
2016-07-26 14:19   ` Robert P. J. Day [this message]
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.1607261016100.14495@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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