On Tue, 2006-12-26 at 20:30 -0900, Jeff Spaleta wrote:
But I want to be clear, this is not a navel gazing exercise, where I
want to dream up the ideal notification tools meant to solve all
maintainer coordination problems and cure cancer. I am looking to
solve a very specific problem. We need a way to prevent undue delay in
correcting packages which are broken by firefox rebuilds (or other
packages) because of changes in the versioned directory tree location
which are currently undiscoverable from an rpm based dependency
checking perspective. We have a situation right now where linked in
libraries are going missing on installed system and our available rpm
based depchecking scripts are not catching it.
Seems to me FireFox's packaging is fundamentally broken if RPM dep
tracking can't detect this already. Some judicious use of virtual
provides and dep-filtering maybe? Since the packages are apparently
dependent on a versioned directory, maybe they all need to just Require:
firefox = 1.5.foo.bar ...