From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] fs/common.mk: move BR2_ROOTFS_POST_FAKEROOT_SCRIPT after pre cmd hooks
Date: Fri, 02 Oct 2020 10:39:01 +0200 [thread overview]
Message-ID: <875z7t2fa2.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200927071547.GG11621@scaer> (Yann E. MORIN's message of "Sun, 27 Sep 2020 09:15:47 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Charles, All,
> On 2020-09-10 17:30 -0700, Charles Hardin spake thusly:
>> From: Charles Hardin <ckhardin@gmail.com>
>>
>> The fakeroot script does not appear to be used in any of the checked
>> in defconfig targets, but it seems that most often the post
>> fakeroot script should be done after all the packages rules have
>> been applied instead of before.
>>
>> Given that a change in systemd moved the SYSTEMD_PRESET_ALL hook to
>> a ROOTFS_PRE_CMD_HOOKS, there was no way to use a FAKEROOT script
>> to disable a service or fixup a systemd configuration. The systemd
>> move makes sense, and this just tries to preserve the same ability
>> to fixup a rootfs after all the cmd hooks are processed.
>>
>> Refer to commit 65b63785a642bbc565924edf365b5d7c080f961c for
>> the change that instigated this reordering.
>>
>> Signed-off-by: Charles Hardin <ckhardin@gmail.com>
> Applied to master, thanks.
Committed to 2020.08.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-10-02 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 0:30 [Buildroot] [PATCH 1/1] fs/common.mk: move BR2_ROOTFS_POST_FAKEROOT_SCRIPT after pre cmd hooks Charles Hardin
2020-09-14 21:20 ` Yann E. MORIN
2020-09-14 22:44 ` Charles Hardin
2020-09-27 7:15 ` Yann E. MORIN
2020-10-02 8:39 ` Peter Korsgaard [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=875z7t2fa2.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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