<p>Skimming through your link to suse's patterns, it's hard to easily grasp it's purpose, while if serving the same purpose, the implementation of is not only extremely confusing, hard to maintain and extremely non-standard fashion, rather than implemented in rpm itself in a proper, intuitively named way for wider adoption.</p>
<p>As the group tag more recently has been made optional, with it's replacement that's not limiting to single tag value, requiring standardized set of groups being moved out of rpm, this is really bad considering cross-compatibility, with functionality tied to distro specific dependency solver.</p>
<p>By rather introducing the trivially implementation of MetaTags:, a proper replacement for group tag is provided in rpm itself where it should be, while the support of multiple meta tags rather than group, aids the vendor specific groups that's not standardized across distros, leaving yet another obstacle for cross-distro packaging compatibility.</p>
<p>I hope this better explains it's purpose, rationale, motivation and benefits of. :)</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/107#issuecomment-266472856">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb80zCUorD0f8vWNBHz9NW1x2LtQeOfks5rHXK7gaJpZM4LGQbJ">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb804FR6kuFj_BOwdZLm4Xr_9sfGo1Mks5rHXK7gaJpZM4LGQbJ.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/107#issuecomment-266472856"></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 #107: Skimming through your link to suse's patterns, it's hard to easily grasp it's purpose, while if serving the same purpose, the implementation of is not only extremely confusing, hard to maintain and extremely non-standard fashion, rather than implemented in rpm itself in a proper, intuitively named way for wider adoption.\r\n\r\nAs the group tag more recently has been made optional, with it's replacement that's not limiting to single tag value, requiring standardized set of groups being moved out of rpm, this is really bad considering cross-compatibility, with functionality tied to distro specific dependency solver.\r\n\r\nBy rather introducing the trivially implementation of MetaTags:, a proper replacement for group tag is provided in rpm itself where it should be, while the support of multiple meta tags rather than group, aids the vendor specific groups that's not standardized across distros, leaving yet another obstacle for cross-distro packaging compatibility.\r\n\r\nI hope this better explains it's purpose, rationale, motivation and benefits of. :)"}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/107#issuecomment-266472856"}}}</script>