http://bugzilla.suse.com/show_bug.cgi?id=981083
http://bugzilla.suse.com/show_bug.cgi?id=981083#c12
--- Comment #12 from Michal Marek ---
To give a more concrete example: kernel-default.spec in SP2 produces a handful
of these "KMPs":
cluster-md-kmp-default
cluster-network-kmp-default
dlm-kmp-default
gfs2-kmp-default
ocfs2-kmp-default
Now all of them depend on the exact version of the main kernel package (we are
not using the ksym() dependencies as we are not sharing the KMPs among
different kernel versions) and there are some dependencies among the packages
themselves (gfs2 and ocfs2 require dlm I think). In order to avoid hard-coding
the dependencies in the spec file, the find-requires script in kernel-source
checks 1) if the given set of *.ko files is one of those KMPs, it generates a
dependency kernel-default = %version-%release 2) if any of the *.ko files
depend on *.ko files from another KMP, it generates a dependency like
dlm-kmp-default = %version-%release. All this requires knowing to which
subpackage do the files on input belong and I'm not sure if the
/usr/lib/rpm/fileattrs based dependency generator has such information. Of
course, we could generate the ksym() dependencies and *somehow* inject at least
the dependency on kernel-default. But it would allow the solver to make choices
like "I'll give you this version of kernel-default and ocfs2-kmp-default, and
since the latter has some funny dependencies, I'll also give you this other
version of dlm-kmp-default and the kernel it depends on". I *hope* the solver
is smart enough not to do this, but expressing the dependencies explicitly is
IMO a safer choice.
--
You are receiving this mail because:
You are on the CC list for the bug.