On Tue, Jan 15, 2008 at 07:44:09PM +0200, Avi Kivity wrote: > Yes, you're right. My confusion arose because we have two distinct needs > for a "kernel directory": > > 1. A build directory for the external module (which really needs to be a > kernel directory) > 2. A directory with the exported userspace headers (like /usr/include) > > We are using one directory for both. Once we separate this, the mess > should be cleared up.
Exactly. Please just bundle the latest required interface headers with the userspace tarball. Take e.g. xfs as an example. This one doesn't just need the whole filesystem layer but also quite a few lowlevel implementation files that are used in libxfs through an kernel API shim layer. Instead of having some fragile dependencies it just ships copies of the kernel files in exactly the version it needs. Resyncing is quite trivial and can be automated with a script. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
