Description of Problem:
Because this package contains unowned directories, they will be created
with the current umask. When having restrictive administrator settings
(umask 077) ordinary user will not have access to them and can not use
Another problem occurs when removing packages. Then orphaned directories
| $ rpm -qf /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle/ApacheTest.pm
| file /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle is not owned by any package
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. umask 077
2. make sure that mod_perl is uninstalled completely
(rm -rf /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle)
3. rpm -U mod_perl-1.99_04-3.i386.rpm
4. ls -l /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle
5. use the programs/scripts/libraries of the package as non-root user
6. rpm -e mod_perl-1.99_04-3
* at 4:
| drwx------ 2 root root 4096 Sep 13 16:19 /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle
* files can not be found/read at 5 and
* /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/Bundle still exists after 6.
The directories in question are intentionally not owned by mod_perl since other
packages put files in there. The real solution to this is probably to make the
perl package create and own all auto and Bundle directories and to fix the other
packages that claim to own them (perl-DBI, perl-DBD-MySQL and perl-DBD-Pg).
I filed this as bug 73970.
rpm allows directories to be shared between several packages. The directory will
be kept when there are existing other packages owning it and removed when there
are no such packages.
Because there are too much perl-XXX bundle packages it makes no sense to let all
possible directories under /usr/lib/perl5 owned by perl or to create perl-XXX
hierarchie packages describing the perl-filesystem.
Jeff Johnson spends a lot of energy into rpm to add features like refcounted
directories, so you should these them ;)
It's not a question of making 'all possible directories under /usr/lib/perl5
owned by perl', merely a question of making perl own
Anyway I'll go with whatever Chip says on this...