core machinery Content-addressed storage and SAT resolution
Conary-owned files are stored by content hash so identical content is kept once.
A SAT solver (resolvo) handles conflicts, virtual provides, and typed
dependencies. Garbage collection of the store follows database reference counts.
conary query deptree nginx conary query depends nginx conary query rdepends openssl conary query whatprovides 'soname(libssl.so.3)' sudo conary system verify
native format Build, sign, verify, and inspect CCS
CCS is Conary's native package format: a CBOR manifest, SHA-256 content
verification, Ed25519 signatures, and FastCDC content-defined chunking for
large files. Signing requires an explicit private key.
conary ccs build . conary ccs sign --key private.pem package.ccs conary ccs verify package.ccs conary ccs inspect package.ccs
changeset-backed Changesets and configuration handling
Every install, update, and remove is a durable changeset with an explicit
pending, applied, failed, or rolled-back outcome. A changeset records database
and file state; it does not imply a bootable generation for every install, and
it does not promise universal filesystem rollback. Configuration files follow
their source format's exact rules.
shared service Remi, the package service
remi.conary.io authenticates the Fedora,
Ubuntu, and Arch repositories, converts their packages to CCS on demand, and
serves them with the source-format lifecycle contract intact. A package can
fail conversion even when upstream serves it fine; that is feedback, not a
verdict on the package. Its first complete signed public universe is still an
open launch gate.
sudo conary repo list sudo conary repo sync remi sudo conary search htop
