<p>I think the problem here is that these macros do use the same name for both the bcond variable and the configure switch. I'd rather think that the interesting cases are where you need to have some high level bcond switch may be even resulting in multiple copnfigure switches of different names.<br>
Using the same name is especially weird for the disable and without cases. I really cannot see the use case where you would have to pass --with-foo just to have foo disabled in the configure script. I can imagine disabling other features while enabling foo.</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/176#issuecomment-297698504">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb806WS1ekcgswTQZ0eda8HWIyvRKY0ks5r0IkQgaJpZM4MbLdt">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb804SIRWkSU5M4gKd3akxw7u_YEHgcks5r0IkQgaJpZM4MbLdt.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/176#issuecomment-297698504"></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":"@ffesti in #176: I think the problem here is that these macros do use the same name for both the bcond variable and the configure switch. I'd rather think that the interesting cases are where you need to have some high level bcond switch may be even resulting in multiple copnfigure switches of different names.\r\nUsing the same name is especially weird for the disable and without cases. I really cannot see the use case where you would have to pass --with-foo just to have foo disabled in the configure script. I can imagine disabling other features while enabling foo.\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/176#issuecomment-297698504"}}}</script>