<p>Seems I missed the return with error code earlier, possibly due to testing by commenting %configure in %prep where this doesn't do anything at all. So it seems to do what it promises in eg spec preample, but spec scriptlets are special for the macro expansion warning already.</p>
<p>I'm not really happy with any of the existing or proposed macros-in-comments hacks. Most of the time expanding macros in comments is perfectly harmless and the warning rpm currently emits is just unnecessary noise, and yet does not warn in many cases where it would matter. And this outlaws commenting multiline macros. Which, if you really think about it, seems totally absurd.</p>
<p>If we end up agreeing that multiline macros are special enough that we need to do something differently wrt them then we might as well do what the user intended and not expand the bleeping line, instead of failing with an unhelpful error.</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/pull/124#issuecomment-273499005">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb806s7NdNim1UwqgJSfcrmZr-rKsgNks5rTimzgaJpZM4Lhpp5">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb809v0CGXKFvBnbNXxrxpR2P2EsC-Vks5rTimzgaJpZM4Lhpp5.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/124#issuecomment-273499005"></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":"@pmatilai in #124: Seems I missed the return with error code earlier, possibly due to testing by commenting %configure in %prep where this doesn't do anything at all. So it seems to do what it promises in eg spec preample, but spec scriptlets are special for the macro expansion warning already.\r\n\r\nI'm not really happy with any of the existing or proposed macros-in-comments hacks. Most of the time expanding macros in comments is perfectly harmless and the warning rpm currently emits is just unnecessary noise, and yet does not warn in many cases where it would matter. And this outlaws commenting multiline macros. Which, if you really think about it, seems totally absurd.\r\n\r\nIf we end up agreeing that multiline macros are special enough that we need to do something differently wrt them then we might as well do what the user intended and not expand the bleeping line, instead of failing with an unhelpful error."}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/124#issuecomment-273499005"}}}</script>