|The interface might change, but there's now a new way to run an Anarki REPL. If you have Racket installed, you can just do this:|
Well, that opens Anarki without changing the current directory. You might want to do this instead if you want to load Anarki's libraries:
$ raco pkg install anarki
$ racket -e "(require anarki) (anarki-repl)"
arc> (prn "Hello, Anarki!")
Racket's raco command supports some other useful operations on installed packages:
$ racket -e "(require anarki) (current-directory anarki-path) (anarki-repl)"
This support came about thanks to kinnard asking what it would take to have an Arc module system, particularly a package manager. I replied with some actionable ideas, and this is the first substantial piece I've implemented.
$ raco pkg update anarki
$ raco pkg remove anarki
Rationale: Anarki code often depends on Racket imports, and if we just piggyback on Racket's package manager, it's going to be pretty easy to declare those dependencies. So let's suppose we're using Racket's package manager. In order to start from a fresh Racket installation and install an Anarki-based Arc project using `raco pkg install`, one of its dependencies needs to be Anarki itself. Now it can be!
So far I've listed myself and akkartik as authors in the Racket package registry, and we have the ability to edit the package description and manage the author list. Anarki is a project where anyone can contribute if they're interested. If you've contributed to Anarki and you're interested in being on the author list, we can make that happen too.