The directory is only included in the "crossfire" package without
a dependency on it:
=> crossfire-client - 1.9.1-3.fc7.i386
=> crossfire-client-images - 1.9.1-3.fc7.i386
=> crossfire-maps - 1.9.1-2.fc6.noarch
Adding a dependency on 'crossfire' from 'crossfire-client' and these others is
not really acceptable, since the client and server packages are not
interdependent (except for this directory).
I could either have multiple packages provide the /usr/share/crossfire
directory, or create a crossfire-filesystem package that contains only this one
Do you have a preference?
Don't make me regret that I've filed lots of tickets about
unowned directories. I have no particular interest in crossfire*,
but as long as it is possible with rpm to install unowned
directories with insufficient file access permission bits,
they remain a source of run-time problems.
A crossfire-filesystem package for a single empty dir would be
ridiculous, especially when it would use default %defattr.
If client and server don't share common files in that directory
and don't use it to exchange files either, how about creating
separate directories for separate packages?
What does upstream say? And how does crossfire-maps fit into the
There are several ways how to fix this, and making all sub-packages
own the same directory would work as a last resort.
I took a closer look at the directory layout and have started testing some
packages that fix these unowned directory issues. I need to finish testing some
additional selinux fixes before I will push an update.
Fixed in rawhide. I'll push updates to F-7 at the same time that I upgrade F-7
to the latest crossfire release.