[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1207191942250.20176@asgard.lang.hm>
Date: Thu, 19 Jul 2012 19:44:55 -0700 (PDT)
From: david@...g.hm
To: Ben Hutchings <ben@...adent.org.uk>
cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Josh Boyer <jwboyer@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Jones <davej@...hat.com>,
Greg Kroah-Hartman <greg@...ah.com>,
Ubuntu Kernel Team <kernel-team@...ts.ubuntu.com>,
Debian Kernel Team <debian-kernel@...ts.debian.org>,
OpenSUSE Kernel Team <opensuse-kernel@...nsuse.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Fedora Kernel Team <kernel-team@...oraproject.org>
Subject: Re: [RFC] Simplifying kernel configuration for distro issues
On Thu, 19 Jul 2012, Ben Hutchings wrote:
> On Thu, Jul 19, 2012 at 06:30:47PM +0100, Alan Cox wrote:
>>
>> For the end user case you need the distro to plonk the right file in the
>> right place and be done with it, once they do that the rest is
>> bikeshedding a ten line Makefile rule.
>
> This might work well for future releases; is there not a need to
> make this work for past releases too?
This approach can work for any 3.x kernel version with any distro. The
distro provides the file, with a new kernel version you do "make
distconfig', with something prior to when this is added you do 'cp
/etc/kconfig/filename .config ; make oldconfig' instead.
the make oldconfig papers over a LOT of differences between the kernel
that the distro built with and the kernel the user is trying to compile.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists