https://bugzilla.redhat.com/show_bug.cgi?id=2084228
Justin M. Forbes <jforbes(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(jforbes(a)redhat.co |
|m) |
--- Comment #11 from Justin M. Forbes <jforbes(a)redhat.com> ---
(In reply to John Kacur from comment #9)
@jforbes(a)redhat.com
We were wondering with the kernel-tools package, does the maintainer of
kernel-tools have to manually add the kernel source every time a new version
of the kernel is available, or are there some kind of hooks that do this for
you?
Yes, on the Fedora side of things, kernel-tools is maintained as a completely
separate package and not as part of the kernel itself. I do handle it manually.
There was a valid reason for the split quite some time ago, though that
reasoning is slightly less valid these days, and I may fold it back into
kernel. Either way, the resulting rpms would not change. For a build schedule,
rawhide builds kernels tools with every linus rc release, but not with the
daily git snapshots. For stable fedora releases, I build it for whatever
version is being used to rebase the releases, and then only rebuild when there
are changes in stable updates which require it, so not with every release. As
rtla is a part of the upstream kernel tarball, it would make more sense just to
add it as a subpackage.
From a RHEL standpoint, kernel-tools subpackages are in the kernel spec, and
built with every kernel. Again, it could easily be added as a subpackage there
with an MR to kernel-ark (and I typically backport kernel-tools changes made to
ark directly to kernel-tools in fedora as well).
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2084228