This cuts out the need for git for our kernel sources and the + and the
end of our versions is now gone. The build remains a bit weird in order
to bundle the initrd into the kernel image but eventually that will be
dropped, leaving the new coreos-kernel eclass pretty tiny.
Bonus: That + at the end of our versions is finally gone!
Providing the kernel source via git is overkill, we do not maintain any
patches on top of the mainline kernel any more and the repository is
huge. As an added benefit this installs the kernel source to the
traditional /usr/src/linux location that Gentoo expects. Hopefully that
will reduce the number of warnings many ebuilds tend to output.
Patches routinely modify the man page source XML, invalidating the
prebuilt man pages provided by release tarballs. Patch the live ebuild
too and require the docbook XML DTDs unconditionally like we did for 215
all the time going forward so this issue isn't forgotten again during
the next version bump.
Another day, another intermittent build failure because the local xml
docbook catalog didn't work right and the xml parser also failed to
fetch the schema over the network. Configure portage to use network
namespaces to prevent such situations from ever working in the first
place so at least the errors are unlikely to be intermittent.
For the sake of completeness use ipc namespaces too but that is less
likely to actually be a factor in our builds.
The upstream cmake eclass has started properly building cmake in
cross-compiler mode so it doesn't attempt to run native code. Without
those checks the test results need to be defined statically.
- Drop the ldconfig patch, now handled in the initrd.
- Shrink the delta with Gentoo where possible.
- Add missing polkit rule, was only in 215 ebuild.
- Always run eautoreconf, required by the -Wl-fuse-ld patch.
- Use "disable" as our one and only unit preset rule.
- Disable the "First Boot Wizard" which isn't useful on CoreOS.
Also-by: Michael Marineau <michael.marineau@coreos.com>
- Support configuring HP iLO, user space should use a container.
- Many ethernet drivers also need a PHY driver but the associated PHY
drivers are not enabled automatically. This change enables all the
ones that appear to be related to ethernet drivers we already ship.
