* Add el-get-check-recipe command
* Add a script test/check-recipe.el
* Mention recipe checker in the document
* Add warnings to el-get-check-recipe
* Use @command instead of @code
* make el-get.info
* Use more expressive name than el-get-check-recipe-1
* test-recipe.sh no longer fails due to missing el-get test directory
* test-recipe.sh and run-test.sh now do better jobs of cleaning up
* All test scripts now specify /bin/bash as interpreter
Otherwise, run-test.sh fails with the error:
(file-error "Opening output file" "no such file or directory"
"/tmp/el-get-test-home/.emacs.d/el-get/.status.el.old")
The use case for el-get 'wait is very thin (setup file only), and fixing it
would be hard enough that we're not going to work on it. If you want to wait
until the packages are installed, just use 'sync.
One reason why fixing that situation is not easy is that some error cases
that happen at install time are not catched by El-Get code, so there's no
place where to set the package status as "failed" or something equivalent.
We wouls still have some "required" packages left, and if we don't count
them in the progress information we hang up completely.
This commit also refresh the test/README content to cope with the recent
status.old backup file, and in passing reformat the file as Markdown.
This adds the ability for recipes to specify a required minimum emacs
version. Attempting to install such a recipe in a lower version of
emacs will result in an error.
This is useful if you are testing the installation of a package with
lots of dependencies, since without cleaning the dependencies will not
need to be reinstalled at the beginning of each test run.
Unlike the other test scripts, this doesn't run a test or install a
recipe or anything. It just opens up emacs with el-get ready to go so
you can do manual testing.
This prevents Emacs from inserting "..." in place of very deep or long
data structures, which could corrupt the status file in some cases.
This is done by defining a wrapper function "el-get-print-to-string",
which el-get should use for all "critical" stringification tasks.
As noted in #689.
