<p>FWIW, automating sub packages was considered by Toby in Unity linux back in 2009 (until there were some NZ earthquakes he had to deal with)),</p>
<p>If you do patterns-through-paths, you are going to recreate SELinux policy maintenance issues: maintaining the patterns globally is rather more abstract than editing spec files. See policy-of-the-day issues with SELinux policies, and the confusion that ensures.</p>
<p>Creation of debuginfo sub packages isn't really relevant to automating sub package manifests. E.g. look at all the recent bugs attempting to merge patterns in *.spec with debug info/src subpkgs (and the current issue with file manifests that is almost certainly related to debug info as well).</p>
<p>Good luck! Have fun! Wanna bet? ;-)</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/issues/329#issuecomment-333793269">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb804C2tmWxc59Yhzxbx9bIlWdYU47Tks5sogKvgaJpZM4PquAz">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb80_EaUasunXPS-8IfGFmgkfnJjN86ks5sogKvgaJpZM4PquAz.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/issues/329#issuecomment-333793269"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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 in #329: FWIW, automating sub packages was considered by Toby in Unity linux back in 2009 (until there were some NZ earthquakes he had to deal with)),\r\n\r\nIf you do patterns-through-paths, you are going to recreate SELinux policy maintenance issues: maintaining the patterns globally is rather more abstract than editing spec files. See policy-of-the-day issues with SELinux policies, and the confusion that ensures.\r\n\r\nCreation of debuginfo sub packages isn't really relevant to automating sub package manifests. E.g. look at all the recent bugs attempting to merge patterns in *.spec with debug info/src subpkgs (and the current issue with file manifests that is almost certainly related to debug info as well).\r\n\r\nGood luck! Have fun! Wanna bet? ;-)"}],"action":{"name":"View Issue","url":"https://github.com/rpm-software-management/rpm/issues/329#issuecomment-333793269"}}}</script>