<p>QUERY and VERIFY bits were consolidated int a single enum to <em>permit</em> patches to be applied from header content at some point, not otherwise.</p>
<p>By all means, one can certainly chose to have separate QUERY and VEIFY logic bits. An equivalent amount (imho) of work on the implementation woul permit applying patches to (usually) configure files from header metadata, which is surely a stronger and more reproducible mechanism than relying on seeds/peel invocations from, say, %post script lets.</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/commit/393879d9c58905027741baf68795523bbdd4a32e#commitcomment-25835832">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb800RhuoukhLKqe5QZHLInwRBgIj2Xks5s53x8gaJpZM4QqR73">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb80yMNET0MU4JCflOhYhDBo41Sj5aNks5s53x8gaJpZM4QqR73.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/commit/393879d9c58905027741baf68795523bbdd4a32e#commitcomment-25835832"></link>
  <meta itemprop="name" content="View Commit"></meta>
</div>
<meta itemprop="description" content="View this Commit 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":"@n3npq on 393879d: QUERY and VERIFY bits were consolidated int a single enum to *permit* patches to be applied from header content at some point, not otherwise.\r\n\r\nBy all means, one can certainly chose to have separate QUERY and VEIFY logic bits. An equivalent amount (imho) of work on the implementation woul permit applying patches to (usually) configure files from header metadata, which is surely a stronger and more reproducible mechanism than relying on seeds/peel invocations from, say, %post script lets."}],"action":{"name":"View Commit","url":"https://github.com/rpm-software-management/rpm/commit/393879d9c58905027741baf68795523bbdd4a32e#commitcomment-25835832"}}}</script>