On Fri, 10 Mar 2006, Axel Thimm wrote: > upstream kernels that are release candidates or git sub-rcs etc. are > versioned in FC/RHEL based on the previous stable kernel release, > e.g. FC5's 2.6.16-rc5-git9 kernel is released as 2.6.15. > > I generally think that's a good idea (e.g. it *is* 2.6.15 with patches > towards 2.6.16 and not yet 2.6.16, and the user is not confused that > he's already running 2.6.16). > > But tons of kernel module projects check on the version of the kernel > and trigger different code bits. These projects depend on the > versioning to decide whether some features exist or not. > > This results to funny external Fedora-patches to these projects that > only last a kernel release and are troublesome to maintain. Yes, this is a nightmare for openswan's KLIPS module. > So there is a wish to keep the versioning in the top level Makefile as > vanilla ships it. That way the checks will be more accurate and > users/upstream/packagers will have less to worry about, less > Fedora-only patching and so on. That is going to be confusing too. > Any thoughts on how to make everyone happy? :) I have no idea :( Paul -- Building and integrating Virtual Private Networks with Openswan: http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
