Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support package specific overrides #14

Open
pprkut opened this issue Sep 17, 2023 · 0 comments
Open

Support package specific overrides #14

pprkut opened this issue Sep 17, 2023 · 0 comments

Comments

@pprkut
Copy link
Owner

pprkut commented Sep 17, 2023

Not every rule is going to be universally applicable. There will always be room for exceptions. However, coding these exceptions directly into the lint checks isn't going to scale very well and may very well impact performance.
Instead, a way to let lintpkg know that a certain warning/error is not applicable is preferable. Still, they shouldn't be hidden completely. There should still be a way to see those warnings/errors, if one wants.

The override functionality from lintian is a pretty close match to that behavior. The idea would be to introduce a /usr/share/lintpkg/overrides directory holding override information per package. The content of such a file would look like this:

# Binary needs to retain debugging info to be useful:
foo: unstripped-binary /usr/bin/foo 

As a start, every file affected should be listed. We can introduce support for wildcards later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant