Re: Changing kernel API / Breaking VirtualBox - update criteria violation?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Nov 22, 2011 at 06:00:43PM +0100, 80 wrote:

> The failure is due to Fedora *non-upstream* versionning scheme,
> VirtualBox has *already* fixes the API/ABI issue upstream relying on
> the kernel version (since 3.2 RC).  It has nothing to do with the
> kernel non-stable ABI policy (which is notorious).
> The least we can do is helping third-party packagers to fix this
> issue, not slamming the door on their face.

The supported way to provide a module for Fedora is to have it in the 
upstream kernel source. Anything else is explicitly not supported.

-- 
Matthew Garrett | mjg59@xxxxxxxxxxxxx
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux