Well, all the real "meat" is in kernel-devel, except for
the
/lib/modules/%{version}-%{release}.%{_arch}/build symlink which is in
kernel. My point was that it seems to make sense to just put that
symlink in kernel-devel as well, that way, you either have kernel-devel
installed (and have all the files and the symlink) or you don't.
As is, if you just have kernel installed (and not kernel-devel), you
currently have a dangling symlink.
Indeed that seems pointless. My only guess about its historic origin
is that it's somehow better for the kernel package to own the
/lib/modules/%{version}-%{release}.%{_arch} directory rather than
the kernel-devel package supplying/owning that directory also just
so it can own the symlink. Cue ominous music for rpm black magic.