Compliance And Redistribution¶
Den combines Buildroot artifacts, Linux, BusyBox, systemd, conda packages, and Den-owned recipes. Redistribution needs explicit compliance work.
This page is not legal advice. It records engineering concerns that need to be handled before publishing binary images.
Buildroot And Kernel Sources¶
Linux is GPL-2.0-only. BusyBox is GPL-2.0. Buildroot output can include many licenses depending on the selected packages.
Before distributing images, generate and retain Buildroot legal information:
make -C build/buildroot-src \
O="$PWD/build/buildroot-output" \
BR2_EXTERNAL="$PWD/buildroot-external" \
legal-info
The invocation must match the external tree and output directory used by
den image early-boot.
Conda Package Licenses¶
The conda system generation includes packages from conda-forge plus Den-owned packages. The generation metadata records the package inventory, but Den still needs a generated license report from package metadata.
The report should include at least:
package name,
version,
build string,
channel URL,
license expression,
artifact URL,
artifact hash.
Den has a first generated conda package report:
den report packages --rootfs build/rootfs --output-dir build/artifacts/reports
ct run package-report
This writes:
build/artifacts/reports/conda-packages.json
build/artifacts/reports/conda-licenses.md
The report is generated from the active staged generation’s conda prefix
metadata. It is useful release input, but it is not a complete legal review
and does not replace Buildroot legal-info, source offers, notices, or a full
rootfs SBOM.
Den-Owned Packages¶
Current Den package recipes are declared as BSD-3-Clause except for
den-systemd, which packages systemd under LGPL-2.1-or-later.
The package license field is not enough by itself. Release artifacts should also carry source provenance and notices where required.
Private Channels¶
Do not redistribute private package-channel artifacts unless rights are clear. Credentialed package reads are a build mechanism, not redistribution permission.
Practical Release Gate¶
Before publishing a Den binary image, require:
Buildroot legal-info output,
conda package license manifest,
rootfs SBOM,
source provenance for kernel, BusyBox, Buildroot, systemd, and Den recipes,
checksums for all generated boot artifacts,
signing metadata for release artifacts.