From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10596 invoked by uid 1002); 3 Oct 2003 09:35:05 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 16971 invoked from network); 3 Oct 2003 09:35:05 -0000 Message-ID: <3F7D4315.1020900@gentoo.org> Date: Fri, 03 Oct 2003 05:36:21 -0400 From: Brad Laue User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030925 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-dev@gentoo.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [gentoo-dev] Speaking of new kernels being added to the tree X-Archives-Salt: 4eae0fdd-a1ad-43eb-aa78-0b210a2af4ef X-Archives-Hash: c38acfaf9353bae4e46f663f7c971ff5 Just reading the suse-sources thread - good idea, but I have a suggestion first. I think we should wait on the inclusion of anything kernel related into the CVS tree until some more thought is put into how we're managing our kernel sources. The kernel team seems to be both the smallest and most behind the times, and this is sad given that they're one of the most important teams involved in the project. We're two kernel versions behind (and don't justify that by claiming 2.4.21 or 2.4.22 had bugs, that doesn't fly), and show no signs of making it to a 2.4.23 release. The kernel team needs more people. It needs to drastically reduce the number of kernels in the tree which are of a customized nature (xfs-sources, gs-sources, wolk-sources) until it can manage gentoo-sources in a timely fashion. The kernel team needs to build a subset of patches which form the core of the gentoo kernel. They then need to enable all the additional features provided by xfs-sources, wolk-sources and gs-sources on a per-use-flag basis, rather than having three kernels to manage, each with three different sets of incompatible patches. There obviously aren't enough resources to manage this. Optionalizing features through the use of USE flags only makes sense. This is how all other things are done in Gentoo. I don't have nor do I intend to create six mozilla ports based on all the different sets of potentially incompatible USE flags present in the one ebuild, because to do so would make it impossible to manage. Why is the kernel any different? Why do many different people manage their own patchsets without collaborating and sharing resources to keep our official one up to date? Brad. -- gentoo-dev@gentoo.org mailing list