data/dune


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

; The four RUNTIME data files, installed into <prefix>/share/colitur/ef/ so a
; `dune install`ed / opam-installed `colitur` can find them (bin/main.ml's own
; [data_dir], which probes the installed layout before the build-tree one).
;
; Deliberately NOT the two allow-lists (expected-divergences.sexp,
; expected-divergences-missalemeum.sexp): those are test fixtures describing
; where colitur and a comparison oracle disagree, read only by
; test_differential.ml / test_oracle.ml, and are meaningless to a running
; `colitur`. Installing them would ship an assertion about lectio's and
; missalemeum's behaviour as though it were calendar data.
;
; If a new runtime data file is ever added, it must be added HERE too -- there
; is no glob, on purpose: a glob would silently start shipping the allow-lists
; the moment someone renamed one, and an omission here fails loudly at startup
; (exit 2, naming the missing file) rather than silently degrading.
(install
 (section share)
 (package colitur)
 (files
  (ef/sanctoral.sexp as ef/sanctoral.sexp)
  (ef/adjustments.sexp as ef/adjustments.sexp)
  (ef/lectionary.sexp as ef/lectionary.sexp)
  (ef/commons.sexp as ef/commons.sexp)
  ; Shipped as runnable documentation, NOT as calendar data: every
  ; celebration in it is invented, with example- slugs. It is what
  ; `colitur --overlay` points at in the man page, so it must actually be
  ; installed rather than only living in the source tree.
  (ef/examples/diocesan-example.sexp as examples/diocesan-example.sexp)))