<blockquote>
<p>Down that path, you'd probably want to add some further restrictions to some interpreters, eg -E / -I / -s for Python etc.</p>
</blockquote>
<p>This would be good idea (cc <a href="https://github.com/encukou" class="user-mention">@encukou</a> <a href="https://github.com/hroncok" class="user-mention">@hroncok</a> <a href="https://github.com/stratakis" class="user-mention">@stratakis</a> <a href="https://github.com/torsava" class="user-mention">@torsava</a>)</p>
<blockquote>
<p>So lets just accept there are valid reasons for both, and not make life unnecessarily hard for either case.</p>
</blockquote>
<p>So for this I think we need (<a href="https://github.com/pmatilai" class="user-mention">@pmatilai</a>) to implement either:</p>
<ol>
<li>Full disabler for brp (but as you mentioned above we don't have consistent way, so do you have suggestion how to do it right?)</li>
<li>Support for exclude paths (as I mentioned above, we don't have file classifiers for brp's so immediate solution would be doing it in shell and my question whether just putting regex user specified to 'find' would be enough or we need to make sure that regex for brp is compatible with RPM regexes... how?)</li>
<li>Both</li>
</ol>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/rpm-software-management/rpm/pull/344#issuecomment-341633258">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb80wn71pWIKqaCND65vLrKJIs5foe5ks5syrodgaJpZM4QO8ad">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb80-a-4MOnbF2aIq1q3qps2a2teYvIks5syrodgaJpZM4QO8ad.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/rpm-software-management/rpm/pull/344#issuecomment-341633258"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rpm-software-management/rpm","title":"rpm-software-management/rpm","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rpm-software-management/rpm"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ignatenkobrain in #344: \u003e Down that path, you'd probably want to add some further restrictions to some interpreters, eg -E / -I / -s for Python etc.\r\n\r\nThis would be good idea (cc @encukou @hroncok @stratakis @torsava)\r\n\r\n\u003e So lets just accept there are valid reasons for both, and not make life unnecessarily hard for either case.\r\n\r\nSo for this I think we need (@pmatilai) to implement either:\r\n\r\n1. Full disabler for brp (but as you mentioned above we don't have consistent way, so do you have suggestion how to do it right?)\r\n2. Support for exclude paths (as I mentioned above, we don't have file classifiers for brp's so immediate solution would be doing it in shell and my question whether just putting regex user specified to 'find' would be enough or we need to make sure that regex for brp is compatible with RPM regexes... how?)\r\n3. Both"}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/344#issuecomment-341633258"}}}</script>