Package Reference¶
Den-owned package recipes live in the separate den-os/den-forge
repository and are built with rattler-build. The Den OS repo consumes those
packages as a normal conda channel before conda-forge.
Package List¶
Package |
Purpose |
|---|---|
|
User-facing Den system manager and |
|
Stage1 init script and profile fragments. |
|
Rootfs layout metadata for loader and compatibility paths. |
|
QEMU boot artifact metadata for supported Den targets. |
|
Base account, NSS, hostname, machine-id, shell, and fstab policy. |
|
Generation record, validate, activate, rollback, and archive install tooling. |
|
Den release metadata and |
|
Minimal systemd PID 1 build for Den system targets. |
|
Den smoke unit, console policy, tmpfiles/sysusers snippets, and systemd layout metadata. |
Local Channel¶
Local package artifacts are written by the sibling forge repo under:
../den-forge/build/conda
The system feature currently uses:
[feature.system]
channels = ["file:///work/build/conda"]
When Den writes the host workspace manifest, that placeholder is replaced by
DEN_PACKAGE_CHANNEL or the default sibling local channel:
file://<absolute path to sibling den-forge>/build/conda
Hosted Remote Channel¶
The release channel root for the current train is:
https://packages.den-os.org/den-forge/den-2026.6
Consumers should use the Den channel first and conda-forge second.
conda search --override-channels \
-c https://packages.den-os.org/den-forge/den-2026.6 \
-c conda-forge \
den
Forge Metadata¶
In den-forge, forge/package-groups.yaml assigns every Den-owned recipe to a
package group. forge/build-order.yaml records the package build order and
explicit dependency edges that the recipe graph cannot infer cheaply yet.
The Den OS repository does not carry this package metadata. den forge ...
commands resolve a forge checkout from the current directory or DEN_REPO.
Channel-policy commands read DEN_FORGE_REPO or the sibling den-forge
checkout when available.
Validate that metadata with:
den forge validate
List packages in build order with:
den forge recipes list
For CI and maintainer workflows, changed packages can be selected from git refs:
den forge recipes changed --base origin/main --head HEAD
Rootfs Layout Conventions¶
Packages can request rootfs files by installing:
$PREFIX/share/den/rootfs-files.d/<name>/rootfs
Packages can request final file modes with:
$PREFIX/share/den/rootfs-files.d/<name>/modes
Packages can request rootfs symlinks with:
$PREFIX/share/den/rootfs-links.d/<name>.links
These conventions let conda packages own rootfs policy without requiring conda
packages to write directly to /.