From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org, Adam Duskett <aduskett@gmail.com>,
Thierry Bultel <thierry.bultel@linatsea.fr>,
Wit <linuxcdeveloper@gmail.com>
Subject: Re: [Buildroot] Fwd: [PATCH] fs/user-initrd: add new method for building customizable INITRD
Date: Wed, 13 Sep 2023 15:30:16 +0200 [thread overview]
Message-ID: <20230913133016.GD2693@scaer> (raw)
In-Reply-To: <20230913114508.70a1ea44@windsurf>
Witold, All,
+Adam +Thierry for dracut
On 2023-09-13 11:45 +0200, Thomas Petazzoni via buildroot spake thusly:
> On Wed, 13 Sep 2023 06:41:48 +0200
> Wit <linuxcdeveloper@gmail.com> wrote:
> > As for now user has not much influence on creation of contents of an
> > INITRD image I've made some proof of concept of some wider idea of
> > creating customizable INITRD image.
> > This patch adds possibility of creating customizable INITRD image by
> > selecting some of packages to install. At the moment it supports only
> > glibc builds but I planned to add support for musl and uClibc as well.
> > I've got also some other plans regarding this patch.
> > This patch adds new submenu in "Filesystem images" main menu.
> >
> > I'm sending this patch for evaluation. If the idea of this patch is ok
> > for you I could take care of developing it.
> >
> > Signed-off-by: Witold Kowolik <linuxcdeveloper@gmail.com>
>
> Thanks for your proposal. A couple of comments:
>
> (1) Your patch is line-wrapped, so difficult to review. Could you use
> git send-email to send your patches?
While at the formatting:
- commit author (i.e. email sender) must match the SoB line
- commit title should be: fs/user-initrd: new filesystem (but see
below)
- commit log should motivat the patch, and provide explanations on how
the patch is "designed" (don't describe, but expalain); also, no
personal message (no "I am ..." "I do..." etc...)
> (2) Have you looked at Dracut and its integration in Buildroot? Because
> to me it does pretty much the same as what you're doing. We know
> Dracut's integration in Buildroot has some shortcomings, but I'd
> rather see them being resolved rather than introduce another new
> mechanism.
Exactly. We have an implementation of dracut, even if rickety, so I too
believe that, if anything, that should be fixed where it is broken,
rather than add a new tool with only a (very limited) subset of the
features that dracut already provides.
> (3) I see you're using a Perl script. We generally try to have most of
> the Buildroot plumbing implemented either in shell or in Python.
> However, it's true that having a Python interpreter on the host is
> no longer required, while having a Perl interpreter is (which would
> go in favor of keeping a Perl script).
We do require perl because some packages need perl as part of their
buildsystem:
- libxml-parser-perl, intltool (496078a0a053 dependencies: add perl as
a mandatory dependency)
- the linux kernel
In Buildroot, nothing requires perl: we have no tooling written in perl,
and I would prefer that stays that way. We however have a lot of python
tooling, so if at all, I'd rather we add python as a requirement (or at
least tht we check for it and disable whatever needs it, or that it
depends on host-python3).
So, let's try and keep perl out of Buildroot, and keep writing python
scripts. At the worst, shell scripts, but not perl.
Regards,
Yann E. MORIN.
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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
next prev parent reply other threads:[~2023-09-13 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEVrM6T=5vb98vVUr4AxNWf7xV6VSLyuNME1HpxW=KVJR1vvQw@mail.gmail.com>
2023-09-13 4:41 ` [Buildroot] Fwd: [PATCH] fs/user-initrd: add new method for building customizable INITRD Wit
2023-09-13 9:45 ` Thomas Petazzoni via buildroot
2023-09-13 13:30 ` Yann E. MORIN [this message]
2023-09-13 14:27 ` Wit
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=20230913133016.GD2693@scaer \
--to=yann.morin.1998@free.fr \
--cc=aduskett@gmail.com \
--cc=buildroot@buildroot.org \
--cc=linuxcdeveloper@gmail.com \
--cc=thierry.bultel@linatsea.fr \
--cc=thomas.petazzoni@bootlin.com \
/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