Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Thierry Bultel <thierry.bultel@linatsea.fr>,
	Adam Duskett <aduskett@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/dracut: allow users to provide their own modules
Date: Sun, 18 Sep 2022 21:36:26 +0200	[thread overview]
Message-ID: <20220918193626.GK1419013@scaer> (raw)
In-Reply-To: <95ed1fd5-7c46-c59e-dc5e-bca4fbd5958a@mind.be>

Arnout, All,

On 2022-09-18 10:57 +0200, Arnout Vandecappelle spake thusly:
> On 17/09/2022 23:19, Yann E. MORIN wrote:
> >On 2022-09-17 22:17 +0200, Arnout Vandecappelle spake thusly:
> >>On 19/08/2022 19:50, Yann E. MORIN wrote:
> >>>Add an option to the host-dracut package, so users can point to a list
> >>>of modules to install.
[--SNIP--]
> >>  In other words, I think this should be moved to cpio.
> >I beg to differ (of course!). ;-)
[--SNIP--]
>  However, looking at it from a usability point of view, that is no longer
> the case. In the head of the developer, what they want to do is to make sure
> the right stuff ends up in their cpio archive. They don't actually care if
> the dracut package is used for that.

A final nail in the coffin of a host-dracut option, is that host-dracut
is not user-selectable; the kconfig symbol does not have a prompt, and
is only selectable by something else, like fs/cpio's dracut option.

On another note, users who had a post-image script that uses dracut from
before we introduced it, were obviously not using host-dracut, but a
dracut from their host, and so they most probably can't use extra
modules in that case, so we do not need to catter to those either.

So, I'll resubmit as you suggested.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-18 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 17:50 [Buildroot] [PATCH 0/4] dracut: extend support and tests (branch yem/dracut) Yann E. MORIN
2022-08-19 17:50 ` [Buildroot] [PATCH 1/4] support/test/cpio: test for pv already done by listing the cpio archive Yann E. MORIN
2022-09-17 20:13   ` Arnout Vandecappelle
2022-08-19 17:50 ` [Buildroot] [PATCH 2/4] package/dracut: allow users to provide their own modules Yann E. MORIN
2022-09-17 20:17   ` Arnout Vandecappelle
2022-09-17 21:19     ` Yann E. MORIN
2022-09-18  8:57       ` Arnout Vandecappelle
2022-09-18 19:36         ` Yann E. MORIN [this message]
2022-08-19 17:51 ` [Buildroot] [PATCH 3/4] fs/cpio: accept a list of dracut.conf files Yann E. MORIN
2022-09-17 20:17   ` Arnout Vandecappelle
2022-09-17 21:10     ` Yann E. MORIN
2022-09-18  8:41       ` Arnout Vandecappelle
2022-09-18  8:46         ` Yann E. MORIN
2022-08-19 17:51 ` [Buildroot] [PATCH 4/4] support/tests/cpio: extend runtime tests Yann E. MORIN
2022-09-17 20:17   ` Arnout Vandecappelle

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=20220918193626.GK1419013@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=aduskett@gmail.com \
    --cc=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=thierry.bultel@linatsea.fr \
    /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