Description of problem:
This is kind of an RFE, however with kernel doing 9k provides this could be regarded as more of a bug. See SuSE's Bug about the problem:
Here is the data I tested with:
% l /tmp/kerns-repo -1
...and an example of the data:
% rpm -qp --provides /tmp/kerns-repo/kernel-2.6.32-19.el6.i686.rpm | wc -l
...then the createrepo data:
% l /tmp/kerns-repo/repodata -1
...and finally the primary.sqlite file both uncompressed and then re-compressed using "xz":
...next I did:
% mkdir /tmp/kerns-repo/1
% mkdir /tmp/kerns-repo/2
% mkdir /tmp/kerns-repo/3
% mv /tmp/kerns-repo/*.rpm /tmp/kerns-repo/1
% ln /tmp/kerns-repo/1/* /tmp/kerns-repo/2
% ln /tmp/kerns-repo/1/* /tmp/kerns-repo/3
...which is a hacky way to get 24 versions of the kernel, instead of 8. Primary sizes again:
...and "time" results:
% time bzip2 -dc /tmp/kerns-repo/repodata/primary.sqlite.bz2 > /tmp/kerns-repo/repodata/primary.sqlite
bzip2 -dc /tmp/kerns-repo/repodata/primary.sqlite.bz2 > 1.19s user 0.13s system 97% cpu 1.352 total
% time xz -9 /tmp/kerns-repo/repodata/primary.sqlite
xz -9 /tmp/kerns-repo/repodata/primary.sqlite 21.57s user 0.57s system 95% cpu 23.145 total
% time xz /tmp/kerns-repo/repodata/primary.sqlite
xz /tmp/kerns-repo/repodata/primary.sqlite 20.96s user 0.24s system 96% cpu 21.945 total
% time unxz /tmp/kerns-repo/repodata/primary.sqlite.xz
unxz /tmp/kerns-repo/repodata/primary.sqlite.xz 0.45s user 0.11s system 95% cpu 0.584 total
...note that "xz -9" and "xz" both produced a 2MB primary.sqlite.
Version-Release number of selected component (if applicable):
However note that this would just be the client side change, we'd also need a createrepo change (and an RHN change) to create the .sqlite.xz files.
Also, in case it wasn't obvious, yes if we _have_ to we can probably delay this until 6.1 _however_ that means anyone installing GA for all of RHEL-6 is going to download a bigger .sqlite.bz2 (and/or anyone who refuses to update yum).
Where if we do the yum change for 6.0, then even if we don't do the server change until later all users will get the benefit.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Quality Engineering Management has reviewed and declined this request. You may
appeal this decision by reopening this request.
Moving to 6.1 ... note that we have the bindings now, so we just need the minor createrepo and yum changes to use it.
Removing the bindings blocker
moving to 6.2.x ... it's not done upstream, yet. And pyliblzma is only just available in Fed-14.
Still not done upstream ... need to think about again, WRT repodata.
Given we opened it, and it's not on in Fedora, and there have been a couple of weird issues when people have tried it outside Fedora ... and that we'd still need to change the server side. I think we can just drop this for RHEL-6.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Not much has changed since comment #12, closing this out.