----- "Alexander Todorov" <atodorov(a)redhat.com> wrote:
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.
If I read "man rpmlint" right, '-f' option is used for specifying
user config, but everything in /etc/rpmlint/*config is considered
system-wide config. Therefore it seems that all *config files in
/etc/rpmlint will be loaded even when -f is used (but source code
inspection can make us more sure).
But this question may not be relevant any more, see below.
----- "seth vidal" <skvidal(a)fedoraproject.org> wrote:
you want to add a new file to EVERY SINGLE pkg?
Yes, that's what I proposed.
A new file which is not, at all, useful on the users system?
And in terms of fedora you want to ad 17000 new files? (1 for each
pkg)
That doesn't seem like a good use of our mirror or our users'
bandwidth,
to me.
If I suppose the config file has 1 kB, then it's 1 kB increase per
package. Or 17000 * 1 kB = 17 MB increase for the whole repo (and that's
not even compressed yet). In the worst case (all pkgs have such configs).
So it didn't seem to me so bad.
As you have correctly noted, Seth, my idea was driven by desire to achieve
the same behavior whether it is run by autoqa, by fedpkg, or just
with plain "rpmlint foo.rpm". I just wanted to do it "properly". I am
quite afraid to be flooded with questions "my rpmlint output is
different from yours autoqa's rpmlint output, how that's possible?".
But I must say your fedpkg idea is very good and solves a big part
of this concern. But still, there are many ways how to run rpmlint and
having different output in different scenarios doesn't seem to me
as a systematic solution.
But I see that you guys have different opinions and I don't intend
to push the mine one. Let's start with the simplest one then - just
having the config file in git and downloading it from there.
----- "James Laska" <jlaska(a)redhat.com> wrote:
Starting with a mechanism that will allow maintainers to
instrument rpmlint overrides, and AutoQA will honor their
overrides during rpmlint execution seems like a good first start.
Let's never forget the KISS principle, right? :) Thank you for
your reminder.