Robby has pointed out the detail that is probably least obvious in this
context: building any given document can consult the builds for all
other documents to set up cross-reference links, and the "skipping"
message is meant to convey that a document's cross-reference
information is not available.
Probably because the indicies have to be rebuilt after any documentation
changes; you're seeing messages that say something about that rebuilding
process, I believe.
(But 'raco setup' is ridiculously complex (as Matthew mentioned recently on
the dev@ list) so there may be something else going on t
I have several decent sized collections, each utilized via a 'raco link -d
/a/b'. I end up doing numerous 'raco setup x' after munging around in a
particular collection set.
A typical stdout from a 'raco setup' always appears to have "mystery"
collection entailment to vary degrees over time. e.g
3 matches
Mail list logo
