Description of problem: F-13 gdb.rpm currently contains /usr/share/gdb/auto-load /usr/share/gdb/auto-load/usr /usr/share/gdb/auto-load/usr/lib /usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.13-gdb.py /usr/share/gdb/auto-load/usr/lib64 /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.13-gdb.py Since F-14 these *.py files will be in libstdc++.rpm (it is so upstream, since gcc-4.5.0 which will be in F-14). libstdc++.rpm will not `Requires: gdb'. libstdc++.rpm should not own: /usr/share/gdb/auto-load/usr /usr/share/gdb/auto-load/usr/lib /usr/share/gdb/auto-load/usr/lib64 gdb.rpm cannot own them as it may not be installed. filesystem.rpm owns: /usr /usr/lib /usr/lib64 Therefore filesystem.rpm should own at least these directories: /usr/share/gdb/auto-load/usr /usr/share/gdb/auto-load/usr/lib /usr/share/gdb/auto-load/usr/lib64 /usr/share/gdb/auto-load/lib /usr/share/gdb/auto-load/lib64 (the last two for *.py in glib2-devel.rpm) Version-Release number of selected component (if applicable): F-14
Is that really required? Filesystem should create and own basic system packages which are in use by the vast majority of users. If the directory is in use only by some specific group of users - in this case I assume users of gdb - so probably developers - filesystem subpackage in gdb and Requires: gdb-filesystem in packages with these python scripts makes more sense to me. This will reduce requirements for gdb and will keep filesystem hierarchy more clean...
sorry ... I meant "Filesystem should create and own basic system directories" - of course ...
OK, I will create gdb-filesystem.rpm, thanks for advice. BTW /usr/lib/debug is now owned by all *-debuginfo.rpms and no one else.
From Jakub: I think gdb-filesystem package is unnecessary. If it is not in filesystem, let it be owned by the < dozen packages that will ever ship pretty printers.