[
https://issues.apache.org/jira/browse/METRON-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924493#comment-16924493
]
Justin Leet commented on METRON-2247:
-------------------------------------
This runs through at least some common rpmlint issues that can show up:
[https://fedoraproject.org/wiki/Common_Rpmlint_issues]
I believe you can have runs that succeed in the dev environment, but that
should still be corrected to meet expectations on an RPM, but could still
potentially cause issues (permissions potentially spring to mind). This is
purely speculative though, I barely qualify as an amateur in regards to RPMs.
As an aside, we should try to brake the habit of calling it "full dev". There
is no more quickdev/fulldev, and it's probably confusing for people new to
Metron. It's just the development environment.
> 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)
