add website and GitHub Pages deployment

2026-09-01 11:23:34 +02:00
parent cb1da62339
commit da28f784a8
48 changed files with 3392 additions and 0 deletions
@@ -0,0 +1,59 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>Kama — Keru OS package manager</title>
+<meta name="description" content="Kama (窯, kiln) is Keru's package manager: a ~225-line shell script that builds every package from source by executing recipes.">
+<link rel="stylesheet" href="assets/css/style.css">
+<link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><text y='.9em' font-size='90'>ける</text></svg>">
+</head>
+<body>
+
+<nav class="top" data-nav></nav>
+
+<header class="pagehead">
+    <p class="crumbs"><a href="index.html">home</a> / kama</p>
+    <h1>Kama — the kiln</h1>
+    <p>Keru's package manager, deliberately small.</p>
+    <span class="tag">窯</span>
+</header>
+
+<section>
+    <div class="wrap">
+        <div class="prose">
+            <p><strong>Kama</strong> (窯, "kiln") is Keru's package manager. It's a pure-shell script of roughly 225 lines that builds every package from source by running the commands in a <a href="kama-recipes.html">recipe</a>. It holds no opinions — matching the distro that ships it. It reads a <code>make.conf</code>, runs recipe commands, and gets out of the way.</p>
+        </div>
+
+        <div class="grid grid-3" style="margin-top:30px">
+            <div class="card"><span class="num">no db</span><span class="h">No package database</span><p>Kama doesn't track installed files in a manifest db. It stages, installs, and moves on.</p></div>
+            <div class="card"><span class="num">no resolver</span><span class="h">No dependency resolver</span><p>Dependencies come from the recipe's <code>deps[]</code> array — explicit, not discovered.</p></div>
+            <div class="card"><span class="num">shell</span><span class="h">Pure shell</span><p>The whole manager is a script. Legible end to end; every decision is something you can read.</p></div>
+            <div class="card"><span class="num">stage</span><span class="h">Staging installs</span><p>Builds into a per-package stage dir, then copies into <code>$ROOT</code> — never smears the live tree.</p></div>
+            <div class="card"><span class="num">tmp deps</span><span class="h">Ephemeral build deps</span><p>Build-time-only dependencies are fetched, built, installed, and purged after use — they never accumulate.</p></div>
+            <div class="card"><span class="num">$ROOT</span><span class="h">Builds anywhere</span><p>Targets <code>$ROOT</code>, so it can assemble a full system in a staging root — exactly what the installer needs.</p></div>
+        </div>
+
+        <div class="prose" style="margin-top:34px">
+            <h3>The philosophy in the manager</h3>
+            <p>Kama embodies Keru's central bet: <em>package managers became more complex than the packages they manage.</em> A resolver, a database, a binary format, a compiled daemon — none of that is needed to honestly manage a source-built system. What's needed is a script that faithfully runs what a recipe says, so the user can read any decision it makes.</p>
+
+            <blockquote>"A package manager doesn't need a resolver to be honest. It needs to be legible — you can read every decision it makes, because every decision is a script or a line in make.conf you can see and change."</blockquote>
+
+            <h3>Where it lives</h3>
+            <p>Kama lives in its own repo, <a href="kama-repos.html">alongside the recipe repository</a> — two small pieces that Keru's installer drives together.</p>
+
+            <div class="callout">Kama is the thing that makes "from scratch" real. It's the kiln that fires your system from the ingredients you pick.</div>
+
+            <p><a href="kama-usage.html">How to use Kama</a> · <a href="kama-recipes.html">How recipes work</a> · <a href="kama-repos.html">The repo split</a></p>
+        </div>
+    </div>
+</section>
+
+<footer data-footer></footer>
+
+<noscript><div style="text-align:center;padding:16px">See the <a href="sitemap.html">sitemap</a> for all pages.</div></noscript>
+
+<script src="assets/js/include.js" data-base="."></script>
+</body>
+</html>