On Sat, Feb 17, 2018 at 11:14 AM, Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote: >>>>>> "NG" == Neal Gompa <ngompa13@xxxxxxxxx> writes: > > NG> The problem with Bodhi is that it's too late. > > I don't disagree, but you've switched up your argument. You made the > statement that Fedora doesn't care about rpmlint so there's no point in > improving it. People do care, and rpmlint is featured in an important > place in an important application. It could even be used for gating, > except that it gives far too many false positives. > You mentioned Bodhi, so I mentioned that where it happens is not helpful. I could have also brought up the general attitude I encounter from people in the mailing list and on IRC that rpmlint is useless and its warnings and errors can be ignored, but that's not solvable without making it a centerpiece in the package build process. I would argue that the way Bodhi shows the update checks is actually indicating that they're _not_ important. They're hidden away, and many times, clicking on that tab will give you nothing but an endless loading screen, which indicates that there's been no priority to ensuring the test data is always accessible, anyway. It is _not_ front and center in mock or koji builds. When tests have failures or warnings, they are _not_ featured on the update page itself. They are still hidden away. Again, making the rpmlint policy that approximates Fedora packaging guidelines is possible, but I don't think it'd be used. > NG> And in both Mageia and openSUSE's case, you can define > NG> <srcpkgname>.rpmlintrc files that are picked up by the build system > NG> to ignore issues that are obvious false positives. > > And of course we have that, too, but it's not used in as many places. > I would definitely want to get the name changed from the terrible > ".rpmlint" before that happens, though. > What do you want it to be? -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
