<p><a href="https://github.com/n3npq" class="user-mention">@n3npq</a> Good to see that extending RPM to support env variable shouldn't be hard, since RPM has the --macros CLI option alrady.</p>
<p><a href="https://github.com/conan-kudo" class="user-mention">@Conan-Kudo</a> It might be risky, but we are doing it anyway. This is request to do it a bit better way then we are doing it now. It would even improve the situation, since currently the macros are placed in <code>/etc/rpm</code> and are always loaded. If there was support for env variable, they could be loaded just when the SCL is enabled.</p>
<p>But actually, if scl-utils installed something which could do the <code>%{load ...</code> as you propose across all the SCL directories, that could do the job as well. Nevertheless, that would probably require some LUA and I am not sure the result would be better.</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/363#issuecomment-347124153">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb806J5ZK387f3oA0q5OWbGdoL6ZNdYks5s6oAkgaJpZM4Qpksy">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb802twTy582EdfPOQbqTOuVteMLiBlks5s6oAkgaJpZM4Qpksy.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/363#issuecomment-347124153"></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":"@voxik in #363: @n3npq Good to see that extending RPM to support env variable shouldn't be hard, since RPM has the --macros CLI option alrady.\r\n\r\n@Conan-Kudo It might be risky, but we are doing it anyway. This is request to do it a bit better way then we are doing it now. It would even improve the situation, since currently the macros are placed in ```/etc/rpm``` and are always loaded. If there was support for env variable, they could be loaded just when the SCL is enabled.\r\n\r\nBut actually, if scl-utils installed something which could do the ```%{load ...``` as you propose across all the SCL directories, that could do the job as well. Nevertheless, that would probably require some LUA and I am not sure the result would be better."}],"action":{"name":"View Issue","url":"https://github.com/rpm-software-management/rpm/issues/363#issuecomment-347124153"}}}</script>