We can see the informative result even when there is a
`ruby.rpmlintrc` file.
The `ruby.rpmlintrc` file does not harm our current manual operation
when someone wants to see the original informative result.
```
$ cat ruby.rpmlintrc
addFilter(r'^ruby.spec:\d+: E: use-of-RPM_SOURCE_DIR$')
```
The rpmlint without `--file` option shows the original information.
```
$ rpmlint ruby.spec
ruby.spec:20: E: use-of-RPM_SOURCE_DIR
ruby.spec:231: W: unversioned-explicit-provides bundled(ccan-build_assert)
ruby.spec:232: W: unversioned-explicit-provides bundled(ccan-check_type)
ruby.spec:233: W: unversioned-explicit-provides bundled(ccan-container_of)
ruby.spec:234: W: unversioned-explicit-provides bundled(ccan-list)
0 packages and 1 specfiles checked; 1 errors, 4 warnings.
```
When using the `--file` option, we can suppress the false positive
intentionally by specifying the message.
```
$ rpmlint --file ruby.rpmlintrc ruby.spec
ruby.spec:231: W: unversioned-explicit-provides bundled(ccan-build_assert)
ruby.spec:232: W: unversioned-explicit-provides bundled(ccan-check_type)
ruby.spec:233: W: unversioned-explicit-provides bundled(ccan-container_of)
ruby.spec:234: W: unversioned-explicit-provides bundled(ccan-list)
0 packages and 1 specfiles checked; 0 errors, 4 warnings.
```
After discussing with Vit now, we agreed with starting to use ruby.rpmlintrc.
His concern, the pain with ruby.rpmlintrc was that the ignoring
specific errors/warnings might trigger to hide unknown or unintended
errors/warnings too.
But seeing above my example using the regular expression almost
perfectly matching "^...$", he changed his mind, and we agreed it's
unlikely that the matching pattern hides the unknown errors/warnings.
I will send a PR to add ruby.rpmlintrc as a small start.
So, let's keep in mind to always use the perfectly matching patterns
or prefix matching patterns that do not hide unknown errors/warnings.
--
Jun | He - His - Him