keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

web: Update "local package assembly" a bit

Browse Source
This commit is contained in:
Colin Walters 2014-01-24 18:27:35 -05:00
parent 514b73c944
commit f22bb4dbb2
2 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
fedostree/web/partials/home.html
View File

@ -158,9 +158,17 @@
</p>
<p>
The problem is making this sort of thing efficient and scalable;
it would require careful integration of the local OSTree repository
and the package manager caching to operate at a speed comparable to
traditional package management.
it would require careful integration of the local OSTree
repository and the package manager caching to operate at a speed
comparable to traditional package management.</p>
<p>There are two primary issues. First, OSTree mandates that the
running tree be immutable, and requires construction of a new
tree. This is just a deep mismatch with how package managers are
built. Second, current package managers are totally unaware of
the existence of the OSTree repository at /ostree/repo which holds
binaries. A naive implementation would just redownload the packages,
which would be quite slow.
</p>
</p>
<h3>Development area: Live updates</h3>
<p>

5
fedostree/web/partials/installation.html
View File

@ -95,8 +95,9 @@
<pre>
ostree admin upgrade
</pre>
<p>Although <tt>yum</tt> is installed, it will operate in read-only mode. Do
not attempt to use it at the moment. See </p>
<p>Although <tt>yum</tt> is installed, it will operate in read-only
mode. Do not attempt to use it at the moment. See the section
on the homepage "Development area: Local package assembly".</p>
<p>But with OSTree, it's possible to atomically transition between
different complete bootable filesystem trees. Let's now try the