On 16.12.2009 11:19, Jean Delvare wrote:
Le mardi 15 décembre 2009 20:08, Jeff Mahoney a écrit :
On 12/15/2009 02:06 PM, Stefan Seyfried wrote:
Then it should be easy to build it as a KMP and provide via the buildservice, shouldn't it?
(I'm not saying that this is better for the user or anything, just pointing out that there is another option)
Yep. That's definitely an option, but ends up actually being more work than just adding it to the tree.
But it offers a much higher degree of flexibility. You can provide several versions of the driver for different categories of users, and they can switch easily if anything goes wrong.
And receive several categories of bugreports..? I mean, KMPs are great for modules that for various reasons (supportability, legal issues) can't be part of the kernel package. But creating more KMPs just because we can?
If building KMPs is hard, then maybe we should work at making it easier.
Agreed, but if the code is going to be taken care of by the same people who take care of the kernel (at least this is how I read Jeff's proposal), then no matter how we try, maintaining the kernel + dozen of KMPs will never be easier than maintaining everything on one place. Think of e.g. fixes in driver subsystems that affect both core code and the drivers - having to fix such things in multiple packages is not gonna be fun. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org