A manager as a dialect needs it, as data (ManagerSpec: the dialect's id, the manager of the ontology it drives, what it guarantees, how it writes an exact version and the status its query of an installed package ends with where there is none), the job a requirement of kind tool asks of it, the command lines of a job, and the plan file that names them. A job is the packages of the tool's binding for this manager; where the tool is at a version, the version is written for the first package.
import { jobOf } from"./manager.ts";
// jobOf(spec, requirement) is a job where the requirement asks this manager, and nothing where it asks another
type ManagerSpec = {
/** The id of the dialect (`apt`). */
readonly id: string;
readonly manager: ManagerId;
rea…(420 characters)
typeManagerSpec= {
/** The id of the dialect (`apt`). */readonlyid:string;
readonlymanager:ManagerId;
readonlysummary:string;
readonlyguarantees:ToolGuarantees;
readonlyversioning:Versioning;
/** The exit status of the query of an installed package that means it is not installed; none where it is not known, and then the dialect has no check. */readonlymissingExit:number|undefined;
};
typePlanLine= {
readonlytool:string;
readonlyversion:string|null;
readonlypackages:readonlystring[];
readonlyinstall:readonlystring[];
readonlycheck:readonlystring[] |null;
/** The exit status of the check that means the package is not installed; none where there is no check. */readonlymissingExit:number|null;
readonlyadmin:boolean;
readonlyverified:boolean;
};
One line of the plan file: what is installed and the commands that do and check it.
The text of a plan file: JSON that says it is generated, with its keys in a fixed order. It names what the steps run, so that the digest of a render covers it.