[ https://issues.apache.org/jira/browse/METRON-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923935#comment-16923935 ]
Dale Richardson commented on METRON-2247: ----------------------------------------- I haven't been able to find a concise description as to what rpmlint checks. The source code for all the individual rpmlint checks are listed at [https://github.com/rpm-software-management/rpmlint/tree/master/rpmlint/checks] I was proposing to leave the checks in as I was not sure whether the tests were important or not. Somethings matter even if only they save you from a painful mistake once every blue moon. Once possibility is to dump rpmlint for everything except release and extra debugging builds. > rpm-docker: Provide an option to bypass running rpmlint > ------------------------------------------------------- > > Key: METRON-2247 > URL: https://issues.apache.org/jira/browse/METRON-2247 > Project: Metron > Issue Type: Improvement > Reporter: Dale Richardson > Assignee: Dale Richardson > Priority: Minor > > I notice that a large chunk of the time that an rpmbuild process takes is > spent running rpmlint. For people using the full dev process to spin up a > Metron cluster, running rpmlint is like running unit-testing - the assumption > is that the author of the code you are running has already done these tests. > I propose that running rpmlint should remain as part of a full dev build, but > that it would be useful to provide an argument that you pass to vagrant that > will cause the running of rpmlint to be skipped. This could speed up the > process of standing up a full dev cluster for those people who want it. > -- This message was sent by Atlassian Jira (v8.3.2#803003)