I was originally thinking about doing that, but since the srfi program needs the greater srfi-common file tree it's part of to be present in $SRFI_HOME to be able to run effectively, I changed my mind. Seemed easier to just check out the repository into the right spot and run chicken-install in it.

Good point. Perhaps there should be an `srfi init` subcommand that git-clones srfi-common under $SRFI_HOME?


Reply via email to