On Friday, July 19, 2019 1:05:44 PM CDT, Takashi Iwai wrote:
Well, that's the difference by how to look at the whole process.
You've got positive results, but it's just merely because someone already worked on it to make things working before you try. That's not DKMS that fixes the build issues by the kernel API changes automagically. You haven't seen the people behind the scene, hence you'd believe it being DKMS as an exposed result.
That said, pushing DKMS into Tumbleweed or Kernel:stable *alone* won't help much as advertised. Someone still needs to step in and resolve the issues quickly. It's irrelevant whether DKMS or KMP. Unfortunately, on openSUSE, a fix for Nvidia or such is often behind Ubuntu simply because fewer developers are interested in it.
And, if the problem is about pure packaging, it should be reported as quickly as possible to Bugzilla, and we're going to address it in timely manner. Switching to DKMS should be discussed only after it's confirmed that this kind of feedback cycle doesn't work well.
Takashi
Not sure if you're aware, but we have a dkms-nvidia package available in the Bumblebee repos that hasn't had to change anything with their dkms setup for quite some time. It is very much "just works". Just take a look at this. It has had ***one*** revision since creation in what seems like 2011 (it's updated by a service), and it has been working that entire time. https://build.opensuse.org/package/view_file/home:Bumblebee-Project:nVidia:l... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org