From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/s6-linux-init: Build also for the host
Date: Wed, 27 Mar 2019 17:55:03 +0100 [thread overview]
Message-ID: <20190327175503.5be2fb03@windsurf> (raw)
In-Reply-To: <20190216212835.25503-2-vadim4j@gmail.com>
Hello Vadim,
I am not familiar with s6, so sorry if I'm asking silly questions in
this review.
On Sat, 16 Feb 2019 23:28:33 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> Add strict dependency for host-s6-linux-init to use s6-linux-init-maker
> on the host during the rootfs generation.
I think the wording is not great here: "strict dependency" does not
mean anything in the typical Buildroot speak. I think you wanted to say
"We add host-s6-linux-init as a dependency of the target s6-linux-init,
so that the latter can use the s6-linux-init-maker program as part of
its build process".
However, I think adding this dependency should belong to PATCH 2/3,
where s6-linux-init is actually changed to use s6-linux-init-maker.
Indeed, as I understand it, it's only starting with PATCH 2/3 that
s6-linux-init will need this program. Is this correct ?
If it is, then PATCH 1/3 should only change s6-linux-init.mk to add the
host variant of s6-linux-init.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-27 16:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 21:28 [Buildroot] [PATCH 0/3] init: Add s6 as init system Vadim Kochan
2019-02-16 21:28 ` [Buildroot] [PATCH 1/3] package/s6-linux-init: Build also for the host Vadim Kochan
2019-03-27 16:55 ` Thomas Petazzoni [this message]
2019-04-02 15:48 ` Vadym Kochan
2019-02-16 21:28 ` [Buildroot] [PATCH 2/3] package/s6-linux-init: Allow to install as init system Vadim Kochan
2019-03-27 18:43 ` Thomas Petazzoni
2019-04-02 15:57 ` Vadym Kochan
2019-02-16 21:28 ` [Buildroot] [PATCH 3/3] package/s6-rc: Allow to integrate s6-rc services Vadim Kochan
2019-03-27 18:54 ` Thomas Petazzoni
2019-03-27 20:35 ` Arnout Vandecappelle
2019-03-27 20:37 ` Arnout Vandecappelle
2019-03-28 14:23 ` Thomas Petazzoni
2019-04-02 16:08 ` Vadym Kochan
2019-03-28 14:22 ` Thomas Petazzoni
2019-04-02 21:23 ` Vadim Kochan
2019-04-02 22:19 ` Vadim Kochan
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=20190327175503.5be2fb03@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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