Closed AlexKnauth closed 9 years ago
Bah. I forgot that merging something that changes the docs breaks them.
As a workaround, you can open "pict3d.scrbl" in DrRacket and run it, and then rebuild from the command line.
Ok, it works now.
So if I end up with another pull request that changes the docs, what should I do to make sure it works, while still avoiding including all the files that running the scribble file produce? What I did this time was I committed, ran the scribble file in drracket, and then in the github program, I clicked "discard changes." Should I not discard those? Or should I discard some of them, but not all of them? Looking at another commit, should I not discard the changes to pict3d/scribblings/pict3d-log.rktd? Why is that necessary in the github repo?
Include that file. It's a recording of all the interactions in the documentation, run on a machine with a known-good configuration (e.g. mine or yours).
When the docs are built in DrRacket, the evaluator creates that file. When the docs are built from the command line, the evaluator reads that file and replays it. See make-log-based-eval
in unstable/sandbox
.
I just tried to install it again from the package server, and I got this error: