From f22bb4dbb2bb6e11a745f2ef4da4358cf6441908 Mon Sep 17 00:00:00 2001
From: Colin Walters
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.
+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. +
diff --git a/fedostree/web/partials/installation.html b/fedostree/web/partials/installation.html index 206101af..0a9a6854 100644 --- a/fedostree/web/partials/installation.html +++ b/fedostree/web/partials/installation.html @@ -95,8 +95,9 @@
ostree admin upgrade-
Although yum is installed, it will operate in read-only mode. Do - not attempt to use it at the moment. See
+Although yum 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".
But with OSTree, it's possible to atomically transition between different complete bootable filesystem trees. Let's now try the