Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:22:10 +0100	[thread overview]
Message-ID: <20190328152210.2bc05d0c@windsurf> (raw)
In-Reply-To: <7bb98b03-837a-2494-3de0-b8267a8b7d56@mind.be>

On Wed, 27 Mar 2019 21:35:51 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:

>  So, I've taken a quick look at all the finalize hooks we have, and there's
> nothing that jumps out as "this you really want to do before the
> overlay/post-build". I'm not sure though how it would interfere with the other
> (non-hook) finalizations we're doing (i.e. removing static libs etc.). Every
> hook would need to be reviewed in detail to be sure it's OK.
> 
>  If such a review is done, I wouldn't mind moving the hooks after the
> overlay/post-build. I've checked the history, and I think the order of things is
> mostly accidental. When post-build script was introduced (commit eed7d8737ad) it
> was put at the end of target-finalize, without specific explanation. However, at
> that time, purgelocales was still done after target-finalize (now it has moved
> to a TARGET_FINALIZE_HOOK so it's done in the beginning). So I think there was
> no real consideration at the time. When the overlay was added, it was put just
> before the post-build script, which makes sense. And around that time,
> everything had moved before the post-build script, so when the
> TARGET_FINALIZE_HOOKS were introduced it made sense to keep that before the
> post-build script as well.

I agree that the order of the steps is definitely not the result of a
lot of thinking, but is mostly accidental.

>  We do have to take into account, however, that this may break existing
> overlays/post-build scripts in surprising ways... So it should definitely be
> mentioned in the release notes!

Indeed, and that makes the change potentially a bit annoying :/

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2019-03-28 14:22 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
2019-04-02 16:08           ` Vadym Kochan
2019-03-28 14:22       ` Thomas Petazzoni [this message]
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=20190328152210.2bc05d0c@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