I fully understand the stated goal that
Lusers can download only the -debuginfo packages they want.
But (as you know since we've argued through 5-6 of these -debuginfo
bug reports), it ain't that simple.
Permitting per-subpackage -debuginfo doesn't solve multilib
file conflicts, nor does it solve the RFE for dependencies
so that -debuginfo is upgraded automagically when a package
is upgraded (ther are other solutions possible, just unrelated
to whether symbols are in one or multiple packages).
In fact, "upgrade" for -debuginfo is a rather different operation
than for other software which largely just needs to know "newer".
For -debuginfo its "newer" in the executable/libraray package that
has to trigger a -debuginfo package upgrade. And that cannot
simply be insturmented by adding Requres: somewhere and
Let yum figger it out!
re comment # 8:
I fully understand the stated goal that
Lusers can download only the -debuginfo packages they want.
But (as you know since we've argued through 5-6 of these -debuginfo
bug reports), it ain't that simple.
Permitting per-subpackage -debuginfo doesn't solve multilib
file conflicts, nor does it solve the RFE for dependencies
so that -debuginfo is upgraded automagically when a package
is upgraded (ther are other solutions possible, just unrelated
to whether symbols are in one or multiple packages).
In fact, "upgrade" for -debuginfo is a rather different operation
than for other software which largely just needs to know "newer".
For -debuginfo its "newer" in the executable/libraray package that
has to trigger a -debuginfo package upgrade. And that cannot
simply be insturmented by adding Requres: somewhere and
Let yum figger it out!