From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/s6-rc: Allow to integrate s6-rc services
Date: Thu, 28 Mar 2019 15:23:46 +0100 [thread overview]
Message-ID: <20190328152346.297748d0@windsurf> (raw)
In-Reply-To: <be747f83-7044-2f47-a3bd-351bb8a59f37@mind.be>
Hello,
On Wed, 27 Mar 2019 21:37:38 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> On 27/03/2019 21:35, Arnout Vandecappelle wrote:
> > If such a review is done, I wouldn't mind moving the hooks after the
> > overlay/post-build.
>
> Something essential I forgot to mention: for this s6 patch, the same approach
> as python should be followed: do it as a TARGET_FINALIZE_HOOK. Too bad that it
> doesn't help for init scripts added in the overlay, but such is life.
The downside is that for custom sysv init scripts or systemd unit
files, you can put them in an overlay/post-build, but for s6 "service"
files, you cannot do that: they must be installed by a package.
But perhaps that is an acceptable thing, at least in a first step.
Vadim: what do you think ? Would you be OK with a solution where only
packages can install s6 service files ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-28 14:23 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
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 [this message]
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=20190328152346.297748d0@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