English Finnish
Unowned Directories
The term "unowned directory" (or "orphaned directory") refers to a packaging mistake where these three things happen:
a package includes files within a directory it creates, but *not* the directory itself
none of the package's dependencies provide the directory either
the directory belongs to your package and does not belong to any core package or base filesystem package that is considered essential/fundamental to any Fedora System.
Unowned directories can cause the following problems.
Inaccessible Directories
A restrictive superuser umask during package installation can create inaccessible directories when installed using the RPM Package Manager older than Fedora 9 and RHEL 5.3 are the first to use RPM which sets umask 0022 always. On platforms with older versions of RPM if the superuser does this:
`+ umask 077+` + `+ yum update+` + `+ [or]+` + `+ rpm -ivh PACKAGE+`
Unowned directories within the updated or installed packages will only be readable and executable by root. This prevents other users from using the files within those directories.
This causes run-time problems for users. For example, unreadable subdirs below %_libdir disable plugins. Unreadable subdirs below %_datadir prevent application data, help texts, and graphics from being accessed.
Several sorts of users fix such permission problems with chmod instead of taking the time to report it as a bug. It is common belief that such bugs are so obvious they would be found by the package maintainer or will be reported by other users.
Directories not Removed
Upon uninstalling the package (or upgrading to another version), the old directory is not removed from the file system because it does not belong in the package in the RPM database.
Especially if directories contain a version number, they clutter up the file system with every update which doesn't remove old directories.
Directories cannot be Verified
Unowned/orphaned directories cannot be checked with rpm -V and not with rpm -qf either.
./configure Scripts can Fail
Upstream source tarball configuration can fail, because it detects the presence of an old but empty versioned header directories or because it is trying to use multiple versioned directories instead of just the latest valid one.