On Tue, Aug 13, 2024 at 07:49:23 -0400, Greg Troxel wrote: > Valery Ushakov <[email protected]> writes: > > > I'm still not entirely sure, why XEN kernels include GENERIC.local in > > the first place though. If one needs a fragile maze of includes just > > to avoid a few lines being copy-pasted, that doesn't feel like a win. > > Having FOO include FOO.local is fine, but we still need a local include > file that is included by substantially every kernel. > > The point is that if I decide that on my systems, I want some device > that isn't on by default, or to tweak something, and I want it on > everything, it should be easy.
That depends on the point of view and the usual practices that you are or are not accustomed to. For example I consider the fact that the kernel that calls itself "GENERIC" may (locally built) or may not (releng built) include certain devices and/or customizations quite confusing. I also almost never do build.sh release and build my kernels manually. I find that way easier and faster - and since I do it manually it's not a problem at all to use a different/custom config file (itstead of being dependent on GENERIC being built automatically and thus requiring a way to smuggle changes into it). I don't intend to discuss the relative merits of these schemes, or to impose mine on everyone - just pointing out that there are equally valid definitions of "easy". -uwe
