On Tue, 2006-07-11 at 10:30 -0400, Jesse Keating wrote:
I'm running into a situation with this rule.
The xorg package set. There is xorg-x11-server-Xorg, and a lot of
xorg-x11-drv-foo packages. The drv packages drop files
in /usr/lib/xorg/modules and /usr/lib/xorg/modules/drivers (lib64 for
obvious places). However, xorg-x11-server-Xorg also puts files there.
Normally we'd say that xorg-x11-server-Xorg must own those directories and
not the drivers. BUT xorg-x11-server-Xorg requires drivers, drivers require
Xorg, insert dep loop here.
I'm no expert on Xorg, but I'm not sure why the Xorg server requires any
drivers. While this is certainly the most common use case, is this
really a hard requires? This looks to be a nasty dependency loop.
The X folks think that when RPM is faced with this, it will make an
arbitrary
decision at where to do the transaction, and there could be a case where
xorg-x11-server-Xorg is removed before a drv package, and unless all the drv
packages own the modules and drivers dirs, those directories could get left
behind.
Every single driver package requires xorg-x11-server-Xorg. RPM should
never remove it before all the driver packages are gone.
Even still, erase ordering is not properly implemented in any shipping
version of RPM. This rule is designed to aid such code if it is ever
written.
~spot
--
Tom "spot" Callaway: Red Hat Technical Team Lead || GPG ID: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader:
http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!