From Fedora Project Wiki
(→Using %ghost: fix cons) |
(→Ignoring alternativized files: more cons) |
||
Line 15: | Line 15: | ||
Cons: | Cons: | ||
* rpm -qf /usr/bin/foo doesn't work | * alternativized files are unowned, which means: | ||
* yum install /usr/bin/foo doesn't work | ** rpm -qf /usr/bin/foo doesn't work | ||
** yum install /usr/bin/foo doesn't work | |||
** repoquery --whatprovides /usr/bin/foo doesn't work | |||
=== Using %ghost === | === Using %ghost === |
Revision as of 19:19, 17 February 2009
Motivation
Current usage of alternatives is inconsistent, and rpm -qf /some/file will often say the file is unowned, even if it's been created by some package, which is especially misleading and annoying in case of binaries.
Solutions
All of the options below are currently used in Fedora packages.
Ignoring alternativized files
Pros:
- less work for packager(?)
Cons:
- alternativized files are unowned, which means:
- rpm -qf /usr/bin/foo doesn't work
- yum install /usr/bin/foo doesn't work
- repoquery --whatprovides /usr/bin/foo doesn't work
Using %ghost
%files ... %ghost %{_bindir}/foo
Pros:
- allows globs and generated file lists
- rpm -qf /usr/bin/foo works
- yum install /usr/bin/foo works
- repoquery --whatprovides /usr/bin/foo works
Cons:
- files owned by multiple packages are forbidden by FPG.
Using Provides:
Provides: %{_bindir}/foo
Pros:
- rpm -qf /usr/bin/foo works
- yum install /usr/bin/foo works
- repoquery --whatprovides /usr/bin/foo works
Cons:
- unwieldy with lots of alternativized files