I named the output binary of the shen-sbcl package as shen-sbcl because I plan to also add shen-chez and shen-haskell and shen-rust and whatever else I can.

Force pushed with license information

@bsima do you need help testing this in OSX ?

FYI, I was able to successfully build the shen-sbcl package under OSX

bash-3.2$ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1
bash-3.2$ nix-build -A shen-sbcl
# ...... snip ......
patching script interpreter paths in /nix/store/cqb82sl7yfr0yag7a73j9c5rmxcd34i6-shen-sbcl-3.0.3
/nix/store/cqb82sl7yfr0yag7a73j9c5rmxcd34i6-shen-sbcl-3.0.3
bash-3.2$ result/bin/shen-sbcl 

Shen, copyright (C) 2010-2015 Mark Tarver
www.shenlanguage.org, Shen 22.2
running under Common Lisp, implementation: SBCL
port 3.0.3 ported by Mark Tarver, Robert Koeninger and Bruno Deferrari
exit REPL with (cl.exit)

(0-) 

FYI, I was able to successfully build the shen-sbcl package under OSX

Cool, I suppose that means we can say that shen-sbcl supports any platform that sbcl supports.

And shen-sources should be supportable on all platforms, since it's just the text files.

@bsima yes. And for the record, I develop primarily on OSX. Both Shen/SBCL and Shen/Scheme run without problems. The binary releases are built and tested by a Travis-CI job that runs on Windows, Linux and OSX virtual machines.

Thanks!