public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: alexandre.belloni@bootlin.com, michael.opdenacker@bootlin.com
Cc: openembedded-core@lists.openembedded.org, docs@lists.yoctoproject.org
Subject: Re: [docs] [OE-core] [PATCH] init-manager-none.inc: have no init manager
Date: Tue, 02 May 2023 15:18:28 +0100	[thread overview]
Message-ID: <e20d1f52fef28bd8236efc791a0beeed1c7a31f5.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230502141402301f77f9@mail.local>

On Tue, 2023-05-02 at 16:14 +0200, Alexandre Belloni via
lists.yoctoproject.org wrote:
> Hello,
> 
> This causes the following error:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/7035/steps/12/logs/stdio
> 
> This is the expected behaviour of the patch but doesn't fit with what
> this particular build (qemuarm-oecore) is testing as we can't run
> testimage without an init. I'm wondering what should be the proper
> course of action here.
> 

INIT_MANAGER didn't used to be a variable and therefore could in theory
be unset. The "none" configuration was designed to cause the system to
fall back to the original behaviour. OE-Core's "nodistro" uses the
fallback.

We could decide just to require this variable to be set to something
but this could potentially conflict with people setting up their init
system "manually" within their own distro.

It is a bit tricky to know what to do in situations like these.
INIT_MANAGER was added to try and help people avoid needing to repeat
certain config fragments.

Cheers,

Richard



      parent reply	other threads:[~2023-05-02 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <175A0DD84C89F64A.26969@lists.openembedded.org>
2023-04-28  9:06 ` [PATCH] init-manager-none.inc: have no init manager michael.opdenacker
2023-05-02 14:14   ` [OE-core] " Alexandre Belloni
2023-05-02 14:17     ` Michael Opdenacker
2023-05-02 14:18     ` Richard Purdie [this message]

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=e20d1f52fef28bd8236efc791a0beeed1c7a31f5.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.com \
    --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