state packages come from github only
Deploy website to GitHub Pages / deploy (push) Canceled after 21s
Deploy website to GitHub Pages / deploy (push) Canceled after 21s
This commit is contained in:
@@ -43,7 +43,7 @@
|
||||
<p>At the first installable release (0.1), the network path is straightforward: wired Ethernet via DHCP, or wireless via <code>nmtui</code>, both handled from inside the installer. <a href="network-setup.html">See the network setup flow.</a></p>
|
||||
|
||||
<h3>What "from the network" means</h3>
|
||||
<p>The installer fetches source tarballs (straight from upstream, or via a mirror when <code>SOURCE_MIRROR</code> is set), pulls recipes from the <a href="kama-repos.html">recipe repository</a>, and builds. The heavy lifting is the compiler on your CPU — which is exactly the point of a source-only, from-scratch distribution.</p>
|
||||
<p>The installer fetches source tarballs (straight from upstream, or via a mirror when <code>SOURCE_MIRROR</code> is set) and pulls package recipes from the GitHub-hosted <a href="kama-repos.html">recipe repository</a>. The heavy lifting is the compiler on your CPU — which is exactly the point of a source-only, from-scratch distribution.</p>
|
||||
|
||||
<div class="callout">If you want fast and prebaked, a binary distro is right there. If you want <em>your</em> machine — built from source to your exact selection — Keru is the one.</div>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user