Re: rpmlint improvements
Saw this, after the initial reply, see below.
Kamil Paral wrote:
> Can you explain? Do you mean that rpmlint will read its default
config
> +
> /usr/share/rpmlint/whitelist/<package> ?
Yes, I would love to if rpmlint has internal support for per-package
config file (the actual path doesn't matter). There are some advantages:
1. rpmlint can use it even if you don't have that package installed, it
simply extracts it from the rpm file.
Extraction can be done no matter where the config file is installed.
2. You can be sure that only relevant config file gets loaded for
your
package. That means you don't waste performance on loaded several
thousand other config files and also you can be sure that no other
config file by accident influences your results.
-f option does this.
3. You surely don't want to have several thousand *.config files
directly
in /etc/rpmlint, it would be a mess. At least one more dir is needed
to keep it separated.
I don't think thousand files in /etc/rpmlint or /usr/share/rpmlint/whitelist is
a big difference. If you have many of them they will fill up the directory no
matter the name.
4. These files should be stored in /etc at all I believe. They are
not
config files, which a system administrator would like to change.
They are more like a definition file. Those file will be changed only
by the package maintainer and will be distributed with next package
release. They should not be in /etc.
5. Package maintainers get the same output on their machines as we do
on ours.
-f <per-package-config> which is enabled by default then sounds like the least
invasive solution.
--
Alexander.