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 368CC1381FA for ; Fri, 30 May 2014 18:00:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B3DB6E093B; Fri, 30 May 2014 17:59:59 +0000 (UTC) Received: from baptiste.telenet-ops.be (baptiste.telenet-ops.be [195.130.132.51]) by pigeon.gentoo.org (Postfix) with ESMTP id A0965E086C for ; Fri, 30 May 2014 17:59:58 +0000 (UTC) Received: from gentoo.org ([94.226.51.153]) by baptiste.telenet-ops.be with bizsmtp id 8Hzx1o00u3JKcCE01Hzx4L; Fri, 30 May 2014 19:59:58 +0200 Date: Fri, 30 May 2014 19:59:13 +0200 From: Tom Wijsman To: gentoo-dev@lists.gentoo.org Cc: rich0@gentoo.org Subject: Re: [gentoo-dev] Anyone with access to genkernel repository? Or should genkernel be p.masked on amd64 profiles? Message-ID: <20140530195913.10e51302@gentoo.org> In-Reply-To: References: <53889F70.1090404@gentoo.org> <20140530181022.6b263cde@gentoo.org> <5388AEF6.7040204@gentoo.org> <5388B13E.5090700@gentoo.org> <20140530185038.464e3bca@gentoo.org> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.23; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/nSf7O7HkOh75lp.FGCt_7Oq"; protocol="application/pgp-signature" X-Archives-Salt: c71f3472-b325-4957-9fa7-af2019a0f722 X-Archives-Hash: e55d2dd0ce99d8e3e4e12ff31005e1a9 --Sig_/nSf7O7HkOh75lp.FGCt_7Oq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 30 May 2014 13:32:54 -0400 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. >=20 > 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. It has always been a kernel build/install/initramfs tool; some people misinterpret it for being a "default big working config" tool, without seeing what else it can do. See /etc/genkernel.conf and `man genkernel`. > I'd stick them someplace where any dev can get to them, and separate > them from the genkernel functional code base. Good idea, we really could use some kind of kernel seeds in the Portage tree; if someone is willing to maintain them, knowing that Pappy has maintained them for years and spoke about it it seems like hard work. Pappy has discontinued and sold his kernel seeds; a Funtoo developer bought it, but we're yet to see the first release of this continuation. =20 > 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. s/devmanual/Gentoo Installation Handbook/ to avoid confusion. Other than that; I agree with this as Genkernel works perfectly itself and its just a small problem in the config that could be solved in various ways, like fixing/forking/splitting/removing the config that come along. --=20 With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D --Sig_/nSf7O7HkOh75lp.FGCt_7Oq Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJTiMbyAAoJEPWZc8roOL/QuGoH/0zyEBLtC+WJALr6cqmWaZUA XNPKsp2Dj0NQTW2jv9QoggUhT33e8ZrYy1ZXdRfKjeBVy+Xf4fiqD8xcjlpG7Eky h0nhXV3ibJuQLgC5RwDGlWgEL0rv0XwV/wfNeCDYGm3yCJME8qmW0Ku7Zl9DYMO4 8CLSw4Zpof/3hBV549yqNdnVnB/Jvja36ke/xO/9j6GaUv4PcMsU65I8Sl8cid1+ nhzo4dceXNMEuuJUxRAu59fX3K88VW0wrN2acdnLg0WJhmkihchxYZFdb/lD06lJ hOiem2ybN4ZRIXerTMyKf+0/ijD6nYMk1fs1C7ybb1owDXmO57v2+lM588evKv4= =vHMw -----END PGP SIGNATURE----- --Sig_/nSf7O7HkOh75lp.FGCt_7Oq--