From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925
Description of problem:
Yum slowly d/ls headers for the base upon first invocation of "yum
update" without any arguments. This is a waste of time, because the
installation process could have installed those headers.
It would be more efficient to just ship a yum-headers.rpm in the
distro so it didn't have to download all these headers from the server
on each machine, and install that rpm by default.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum update
Actual Results: It tries to get all the headers in
/var/cache/yum/base/ as well as in /var/cache/yum/updates-released/
Expected Results: The headers in /var/cache/yum/base/ should have
In principle, yum's cache could have been primed by
preparing a package with all the correct headers, yes.
In reality, packages tend to change too rapidly to keep
a yum-headers package up-to-date. Furthermore, it just changes the
problem of cache priming from slow on yum out-of-box to
slow downloading of the yum-headers package before
running yum for no overall win. Sooner or later the user
needs to populate yum's cache with headers.
The current scheme is more flexible but cruder.
Better solutions are in the the works using xml instead of headers.
WONTFIX until then.