The slashpackage quick reference handbook

Initially written starting 20:24 UTC on the 9th of October, 2022 a.d. by Amelia Bjornsdottir (she, they)

This page wouldn’t exist without J. de B. P.’s page on the same matter. This page is meant to be a comprehension of that one, with

General structure of a package (folk will be confused if this is not followed)

Directories, by purpose. Sorted by second column (purposes grouped together, no particular order) if possible.

Structure of package/

TODO: fill this out based on packages as well as the J. de B. P. page on the matter.

Structure of conf-compile (Jarc)

Jarc’s sptools shell scripts are as thick as stirred cornflour wash with his own idioms. Here is the best I could make. I also downloaded and unpacked /pkg/cr.yp.to/prog/prjlibs-2020.05.04 for study, which has provided some edification (although the git repository underlying it did not - it doesn’t contain everything you need to compile a development snapshot of prjlibs. Neither does the sptools counterpart).

Putative get_confcompile_variable function

In pseudocode:

string get_confcompile_variable (string variable)
{
 string filename = "conf-compile/";
 string deffilename = "conf-compile/defaults/";
 filename += variable;
 deffilename += variable;
 if exists(filename) {
  get_firstline(filename);
 } otherwise {
  get_firstline(deffilename) or panic;
 }
}

In English: If exists a file named variable in conf-compile, the value is the first line of the file named variable in conf-compile. Otherwise, it is the first line of the file named variable in defaults in conf-compile. In default of even that, unstudied as of this revision.

conf-compile variables (Jarc)

Unless specified as host/n/…, all packages named here are to be assumed as named under the authority of cr.yp.to, and to be visible in the filesystem at /pkg/cr.yp.to and /package.