On Wed, 2008-02-27 at 17:48 +0100, Alexander Graf wrote: > On Feb 27, 2008, at 5:34 PM, Avi Kivity wrote: > > > Hollis Blanchard wrote: > >> It is a centrally co-ordinated effort, but it is not a package a > >> distro > >> would carry. It is code shared by anything that needs to load a > >> PowerPC > >> Linux kernel, for example: the kernel bootwrapper (part of the Linux > >> source tree), u-boot firmware, Xend, and now qemu. > >> > >> Accordingly, a libfdt.rpm simply doesn't make sense, and the code is > >> intended to be copied into any codebase that needs it. > >> > > > > A static library + headers (i.e. libfdt-devel.rpm) could have been > > used, though Linux avoids external dependencies. > > Why don't you try to talk to the other possible users and create a > version of the library, that at least can be packaged, even though for > now KVM would be the only user? Maybe others (unlikely Linux, maybe > Xen, probably dtc) would like to have a central library for device > trees too.
I think it's obvious that Linux and uboot will never use this. Unless someone steps up to continue PowerPC Xen development, neither will Xen. So you've now narrowed down the use case to dtc (which is libfdt upstream) and qemu. Whose problem are you trying to solve? It doesn't seem to be one that any existing users have. If you want to push it, you should probably propose it on [EMAIL PROTECTED] , which is where libfdt is discussed. I'm sure as hell not going to advocate creating a standalone library, push it into every package that supports PowerPC, and then telling users they must build on a supported version of a supported distribution. -- Hollis Blanchard IBM Linux Technology Center ------------------------------------------------------------------------- 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
