<p>So something I've seen in SUSE systems is that they have a brp-suse script, that reads from a drop-in directory containing brp scripts. They do this because we don't have a way of specifying vendor brp scripts out of the box in RPM.</p>
<p>If vendors want to have more build root policies, they have to redefine the main thing and add to it. This is clunky, inelegant, and means that as things are fixed in RPM upstream, they won't apply to the distribution using the vendor config. This could lead to quirks and breakages, too.</p>
<p>So I think a really simple enhancement would be to make it so that we support drop-in brp scripts like we do for macros and add a vendor search directory, too.</p>

<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/issues/308#issuecomment-355585959">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb80583EXPL-imijy7eFrEu-HIYnX-Wks5tHkMigaJpZM4O-hxn">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb808v1lAn4X24IWf5FtCCrTe6-TR2yks5tHkMigaJpZM4O-hxn.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/issues/308#issuecomment-355585959"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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":"@Conan-Kudo in #308: So something I've seen in SUSE systems is that they have a brp-suse script, that reads from a drop-in directory containing brp scripts. They do this because we don't have a way of specifying vendor brp scripts out of the box in RPM.\r\n\r\nIf vendors want to have more build root policies, they have to redefine the main thing and add to it. This is clunky, inelegant, and means that as things are fixed in RPM upstream, they won't apply to the distribution using the vendor config. This could lead to quirks and breakages, too.\r\n\r\nSo I think a really simple enhancement would be to make it so that we support drop-in brp scripts like we do for macros and add a vendor search directory, too."}],"action":{"name":"View Issue","url":"https://github.com/rpm-software-management/rpm/issues/308#issuecomment-355585959"}}}</script>