From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0DBD21381FA for ; Fri, 30 May 2014 17:40:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id E380DE094E; Fri, 30 May 2014 17:40:32 +0000 (UTC) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D9FE3E0928 for ; Fri, 30 May 2014 17:40:31 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id f8so1493370wiw.14 for ; Fri, 30 May 2014 10:40:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type; bh=ttaE/xZYetG5AlTBR6Ok2JzjzlcmyK1qx4mbcsUGt2s=; b=Ie/Qvws8/1DBQnDtbJJHNYKTeaGiYx9dvPylTN43krC5v+5sWC1eONz56fz/g6akdk AoYY9cBH7mdFlvjKd4BMkE0Oyh+J9bCXHmsSiF3vkpggBkS72UgKyfcnJlwkULkO1VZ5 pEjOY1ndyxhh522DbNilQMRuBdByAUleqsdmp8hKt3zY2L1xg7r7c+HVIFjQ30U/Ele/ 0tTj/MJXcDU580rshrgEXkK2uovz0Oy0uA203gt1jmtmSsdG4W7VGOcTg1QQqGrhe8cu 5y7v0vPy8qZLbm5uccoJ+vSYVGhxbeLUeZfZnkX+5E2Jvoma4YRbigH0uC8XtdPJU3dW nU7g== X-Gm-Message-State: ALoCoQl9zX2yXW8RW96OuJiZAdlParT5yEaaU5Y5dPu+BVwf1WOcyWk18pyj64hSIqUn4yzTjx6U X-Received: by 10.194.71.71 with SMTP id s7mr24559728wju.48.1401471629272; Fri, 30 May 2014 10:40:29 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Sender: lxnay@sabayonlinux.org Received: by 10.194.86.6 with HTTP; Fri, 30 May 2014 10:39:49 -0700 (PDT) In-Reply-To: References: <53889F70.1090404@gentoo.org> <20140530181022.6b263cde@gentoo.org> <5388AEF6.7040204@gentoo.org> <5388B13E.5090700@gentoo.org> <20140530185038.464e3bca@gentoo.org> From: Fabio Erculiani Date: Fri, 30 May 2014 18:39:49 +0100 X-Google-Sender-Auth: N7uNuogG_FZ-zQSU0V4uPBolBTg Message-ID: Subject: Re: [gentoo-dev] Anyone with access to genkernel repository? Or should genkernel be p.masked on amd64 profiles? To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: efaa4778-d08f-4c34-a3ca-dff41b76cc2a X-Archives-Hash: 47556185ce36328ab40ee39112e7e04b configs should have never gotten into genkernel in the first place. it's each kernel pkg (or even version) that owns a valid config of itself. I am part of genkernel@ but I have no will nor time to fix it. And when I have, I'd rather work on genkernel-next, that comes with a much more readable initramfs code (that I managed to rewrite myself). Wiping the whole config files has been on my agenda for very long time already. On Fri, May 30, 2014 at 6:32 PM, Rich Freeman wrote: > On Fri, May 30, 2014 at 1:02 PM, Ben Kohler wrote: >> As nice at it sounds to just DROP these configs, that option is not really >> feasible considering the way we currently use genkernel in our handbook. >> Relying on the kernel's own defconfig, "genkernel all" will NOT produce the >> same mostly-usable-on-any-hardware result that we now rely on. > > Considering that the configs are more generically useful than > genkernel, having them separately maintained sort-of makes sense. > Then genkernel is a kernel build/install/initramfs tool, not a config > management tool. > > I'd stick them someplace where any dev can get to them, and separate > them from the genkernel functional code base. > > As far as who takes care of them goes - I suggest that this stuff > comes out of the devmanual unless somebody steps up to take care of > them. Those who take care of them become those who want to keep them > around. You can't toss out a tool and ask for it to be a > recommendation but point to others that you think need to maintain its > configuration. > > Rich > -- Fabio Erculiani