<p>Hi <a href="https://github.com/herrold" class="user-mention">@herrold</a> - I read your comment a few times and I'm confused...isn't that what my patch is doing?</p>
<p>BTW, it's easy to try an rpm-ostree based system, see <a href="https://getfedora.org/atomic/">https://getfedora.org/atomic/</a> and <a href="https://pagure.io/workstation-ostree-config">https://pagure.io/workstation-ostree-config</a> for example.  One thing I'd note though is that the rpm database is read-only from the point of view of everything <em>except</em> rpm-ostree - we support both <a href="https://www.projectatomic.io/blog/2016/07/hacking-and-extending-atomic-host/">package layering</a> and <a href="http://www.projectatomic.io/blog/2017/06/rpm-ostree-v2017.6-released/">live package layering</a>.  But even when doing live changes, the system still appears read-only to everything else due to some underlying ostree magic.</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/320#issuecomment-327962015">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb808yvt0bgWi-RCs_LGqOxxOxBGOeuks5sgIO1gaJpZM4PQJtL">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb800rij6WVXTP-mWPss4pHlDhWdHejks5sgIO1gaJpZM4PQJtL.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/320#issuecomment-327962015"></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":"@cgwalters in #320: Hi @herrold - I read your comment a few times and I'm confused...isn't that what my patch is doing?\r\n\r\nBTW, it's easy to try an rpm-ostree based system, see https://getfedora.org/atomic/ and https://pagure.io/workstation-ostree-config for example.  One thing I'd note though is that the rpm database is read-only from the point of view of everything *except* rpm-ostree - we support both [package layering](https://www.projectatomic.io/blog/2016/07/hacking-and-extending-atomic-host/) and [live package layering](http://www.projectatomic.io/blog/2017/06/rpm-ostree-v2017.6-released/).  But even when doing live changes, the system still appears read-only to everything else due to some underlying ostree magic.\r\n\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/320#issuecomment-327962015"}}}</script>