On Thu, 2006-12-21 at 10:10 -0500, Andrew Overholt wrote:
On Thu, 2006-21-12 at 13:46 +0100, Axel Thimm wrote:
Instead an analysis would show why packagers used this method and whether we can offer better workarounds for what they wanted to achieve.
In the Eclipse SDK package set, we recently went through the multilib-ification process. We had to add a few file-level dependencies to get this to work. This was due to the inability to specify %{arch} in a Requires. How would this have been better accomplished?
Ben can probably explain this better than I can.
Honestly, this is the only valid case for file-level dependencies I can think of, and unfortunately, the only way to work around it is to fix rpm to permit %{arch} specific Requires.
~spot