Hi!
The discussion moved into a different direction, but nevertheless a few quick comments:
On 06.10.2011 18:00, John W. Linville wrote:
[...] Isn't this just a big kmod package?
No, or at least not exactly. Existing kmod package standards require a separate kmod build for every kernel build. Most (or all?) of them require complex versioning to distinquish between versions of the kmod package and versions of the target kernel. They are a nightmare to maintain.
That's a bit misleading from my point of view, but whatever, likely not worth arguing over the details.
Worse, they require multiple kmod packages for multiple drivers, multiplying the maintenance burden.
See kmod-staging in RPM Fusion for an example of a kmod package (kmod2 to be precise) that contains contains multiple drivers.
diff --git a/depmod-dist.conf b/depmod-dist.conf index 8513288..0585676 100644 --- a/depmod-dist.conf +++ b/depmod-dist.conf @@ -3,4 +3,4 @@ #
# override default search ordering for kmod packaging -search updates extra built-in weak-updates +search updates extra backports built-in weak-updates
And what exactly would be the difference between "updates" and "backports"? Might be wise to at least mention it with a sentence or two in the docs if there is actually one. Is there is: Is it relevant for users or just creating confusion?
Cu knurd