From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2 1/4] kernel-install.eclass: Install logic for dist-kernels
Date: Tue, 07 Jan 2020 07:11:17 +0100 [thread overview]
Message-ID: <7a2681fa5c716250c85f0190672635ab1b588afd.camel@gentoo.org> (raw)
In-Reply-To: <robbat2-20200105T072322-014212601Z@orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
On Sun, 2020-01-05 at 07:30 +0000, Robin H. Johnson wrote:
> On Sun, Jan 05, 2020 at 07:27:38AM +0100, Michał Górny wrote:
> > Introduce a new eclass that contains common logic needed to test
> > and install distribution kernels. This is the eclass common both
> > to kernels built from source and installed from binary packages.
> I'm 100% in favour of the concept here, but I have some implementation
> concerns.
>
> For the (public) record, Infra has been wrapping genkernel to build
> binary kernel + initramfs for internal usage for 5 years now.
>
> Conceptually, can you clarify why you are depending on dracut here,
> rather than using genkernel's initramfs mode?
For a start, because dracut is not bundling all its dependencies. It's
also tested outside Gentoo, so it has much wider testing than genkernel,
and doesn't suffer from intermediate deaths, -next forks and total
confusion over which version should be used.
> I'm not sure you're going to get correct build output in cases like
> x86_64 -> x86 cross-compiles.
Cross-compile support is untested, and provided merely where it was
clear how to do it. I'm happy to fix it later, when someone figures it
out.
> Why not call genkernel from the ebuild instead of re-inventing the
> wheel to compile the kernel yourself.
Have you read the logic and found a way to achieve all that from
genkernel, without 1) losing advantages of my approach, 2) adding a huge
dependency to replace 5 lines of code?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2020-01-07 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 6:27 [gentoo-dev] [PATCH v2 1/4] kernel-install.eclass: Install logic for dist-kernels Michał Górny
2020-01-05 6:27 ` [gentoo-dev] [PATCH v2 2/4] kernel-build.eclass: Build " Michał Górny
2020-01-06 17:43 ` Mike Gilbert
2020-01-06 17:54 ` Michał Górny
2020-01-06 18:07 ` Mike Gilbert
2020-01-06 18:13 ` Michał Górny
2020-01-05 6:27 ` [gentoo-dev] [PATCH v2 3/4] sys-kernel/vanilla-kernel: Migrate to kernel-build.eclass Michał Górny
2020-01-05 6:27 ` [gentoo-dev] [PATCH v2 4/4] sys-kernel/vanilla-kernel-bin: Migrate to kernel-install.eclass Michał Górny
2020-01-05 7:30 ` [gentoo-dev] [PATCH v2 1/4] kernel-install.eclass: Install logic for dist-kernels Robin H. Johnson
2020-01-07 6:11 ` Michał Górny [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=7a2681fa5c716250c85f0190672635ab1b588afd.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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