The intended-use notice is one of the guards every board here carries, and at the
moment it is a file somebody has to find. An operator who downloads a binary and
runs it never opens the repository, so for them the notice does not exist.
Carry it to where the software is.
The runner prints a short pointer to the notice and the licence in its help output
and in its version output, naming the files rather than restating them. Restating
drifts, and the version somebody has in front of them is then a paraphrase of a
document that has since changed.
The release carries the notice, the licence and the privacy document alongside the
binary, so an operator who downloads one file and never visits the repository still
has all three in the same directory.
Two limits worth writing at the code rather than only here. A notice is not a
control and printing it prevents nothing, so it should not be counted as one when
somebody later asks what stops misuse. And a notice an operator has to run a verb to
see is weaker than one in the download, which is why both routes exist rather than
either alone.
Done when lab --help and the version output both name the notice, the licence and
the privacy document, and the release archive contains all three files next to the
binary.
The intended-use notice is one of the guards every board here carries, and at the
moment it is a file somebody has to find. An operator who downloads a binary and
runs it never opens the repository, so for them the notice does not exist.
Carry it to where the software is.
The runner prints a short pointer to the notice and the licence in its help output
and in its version output, naming the files rather than restating them. Restating
drifts, and the version somebody has in front of them is then a paraphrase of a
document that has since changed.
The release carries the notice, the licence and the privacy document alongside the
binary, so an operator who downloads one file and never visits the repository still
has all three in the same directory.
Two limits worth writing at the code rather than only here. A notice is not a
control and printing it prevents nothing, so it should not be counted as one when
somebody later asks what stops misuse. And a notice an operator has to run a verb to
see is weaker than one in the download, which is why both routes exist rather than
either alone.
Done when
lab --helpand the version output both name the notice, the licence andthe privacy document, and the release archive contains all three files next to the
binary.