492260 – Suggest using upstream default config of kernel, instead of genkernel version

Bug 492260 - Suggest using upstream default config of kernel, instead of genkernel version

Summary: Suggest using upstream default config of kernel, instead of genkernel version

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Hosted Projects
Classification:	Unclassified
Component:	genkernel (show other bugs)
Hardware:	All Linux

Importance:	Normal enhancement (vote)
Assignee:	Gentoo Genkernel Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2013-11-21 23:28 UTC by Raymond Jennings
Modified:	2017-09-07 00:48 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Raymond Jennings 2013-11-21 23:28:56 UTC

upstream kernel already has sane built in default config, and I've seen a few bugs where genkernel doing it the hard way is causing problems.

Suggest letting genkernel use whatever the kernel's own default config is.

Reproducible: Always

Comment 1 Ben Kohler gentoo-dev

2013-11-22 00:25:05 UTC

Upstream config is not going to enable NEARLY enough drivers for a usable "genkernel all" for most users.  Genkernel's configs need reworking, but I'm fairly sure that using upstream configs is NOT going to be the solution.

Comment 2 Rick Farina (Zero_Chaos) gentoo-dev

2013-11-22 01:18:22 UTC

how about "allyesconfig"?

Comment 3 Raymond Jennings 2015-08-30 18:49:36 UTC

What about maintaining the genkernel specific portion as simply a diff against the upstream default?

Might make it easier to maintain when upstream changes.

Comment 4 Robin Johnson archtester

2017-09-07 00:48:35 UTC

This is already done with the newer kernel-generic-config + arch-config stuff.