<p>I've removed the redundant --target from rpmspec now, but I'm uncertain about what you mean by the one specific to rpmbuild as it's identical and redundant as well.</p>
<p>As it therefore has the exact same behaviour as the global --target, the only difference seems to be that it's part of the --help options specific to rpmbuild, which states the following:<br>
--target=CPU-VENDOR-OS     override target platform</p>
<p>Then for the global --target option, listed below "Common options for all rpm modes and executables:":<br>
--target=CPU-VENDOR-OS     Specify target platform</p>
<p>So that's pretty much the only differences between the two I find, for which I personally think the latter global one as the more sensible (especially for rpmbuild where "override target platform" is rather ambigious..</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/142#issuecomment-290976191">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb802InOhqBNRNJ4FZpdcqIx3a6es7gks5rr3BXgaJpZM4LyaTG">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb804RmY7zkp7pdMhR27G9aXkRHXBCYks5rr3BXgaJpZM4LyaTG.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/142#issuecomment-290976191"></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":"@proyvind in #142: I've removed the redundant --target from rpmspec now, but I'm uncertain about what you mean by the one specific to rpmbuild as it's identical and redundant as well.\r\n\r\nAs it therefore has the exact same behaviour as the global --target, the only difference seems to be that it's part of the --help options specific to rpmbuild, which states the following:\r\n      --target=CPU-VENDOR-OS     override target platform\r\n\r\nThen for the global --target option, listed below \"Common options for all rpm modes and executables:\":\r\n      --target=CPU-VENDOR-OS     Specify target platform\r\n\r\nSo that's pretty much the only differences between the two I find, for which I personally think the latter global one as the more sensible (especially for rpmbuild where \"override target platform\" is rather ambigious.."}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/142#issuecomment-290976191"}}}</script>