On Sat, 31 May 2014 22:42:17 +0100 Fabio Erculiani <lx...@gentoo.org> wrote:
> On Sat, May 31, 2014 at 9:06 PM, Robin H. Johnson > <robb...@gentoo.org> wrote: > > No, I don't agree that kernel configs "belong" to kernel packages. > > In general, barring the crazy option explosion, these are meant to > > be stock working configs that should in combination with ANY kernel > > package, produce a working kernel. > > > > Then you are just moving the problem around. > I believe that kernel configs should be provided by their own kernel > packages (and there are some, not just gentoo-sources) because it is > much easier to keep them in sync on every new release and deal with > each version separately if/as needed (including testing!). How are you > dealing with config var name changes between different kernel versions > or just different pkgs then? Different packages is not a problem; since the difference in terms of config between separate packages is small enough, a dozen of options. Different version may be a problem, a rather small one; nothing prevents one from keeping config options around for both versions. > You cannot possibly support all kernel versions for all kernel pkgs > available in tree with just one single config file in a sane, clean > and maintainable way, hoping that a change in this file will not > affect previous or future kernel releases. How are you going to test > your config changes against old kernel pkgs? Each test is quite > expensive to run. > > Good luck with that :-) Does it really need to be sane, clean and maintainable for it to work? Yes, maybe; but how sane, clean and maintainable? We can do better... A fork (eg. hardened-sources config, geek-sources config) where needed might still be a way out; however, one should consider to look into a better architecture than plain forks. For example, a config that sources a generic config and adds hardened changes on top of that; kind of like the way GRUB 2's /etc/grub.d/ config generation works. We should introduce this only when needed to avoid to over-design it. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
