(kernel vs kernel-headers source packages) |
(clean irc log) |
||
| Line 8: | Line 8: | ||
19:26 < Stskeeps> mcfrisk_: kernel (or adaptation kernels) has to be that | 19:26 < Stskeeps> mcfrisk_: kernel (or adaptation kernels) has to be that | ||
version or higher | version or higher | ||
| - | |||
19:27 < mcfrisk_> ok, just feels odd that they come from different source | 19:27 < mcfrisk_> ok, just feels odd that they come from different source | ||
package which are kept in sync behind the curtains.. | package which are kept in sync behind the curtains.. | ||
It feels a bit strange that kernel package does not Provide kernel-headers. If userspace needs to access some driver/adaptation specific header file, they need to do it through the kernel-devel package. | It feels a bit strange that kernel package does not Provide kernel-headers. If userspace needs to access some driver/adaptation specific header file, they need to do it through the kernel-devel package. | ||
Would be nice to have here an explanation why there are separate source packages for kernel and kernel-headers. From irc answer is:
19:25 < mcfrisk_> Hello, does anyone know why meego has different source
packages for kernel and kernel-headers?
19:26 < Stskeeps> mcfrisk_: kernel-headers basically defines the common kernel
api
19:26 < Venemo> Stskeeps, hey, this seems to be performing very nicely
19:26 < Stskeeps> mcfrisk_: kernel (or adaptation kernels) has to be that
version or higher
19:27 < mcfrisk_> ok, just feels odd that they come from different source
package which are kept in sync behind the curtains..
It feels a bit strange that kernel package does not Provide kernel-headers. If userspace needs to access some driver/adaptation specific header file, they need to do it through the kernel-devel package.