ros-install(1)
π NAME π
okay bestie, this is the ros-install(1) page β the glow-up manual for installing lisp implementations or a quicklisp system. Itβs giving βmake your lisp setup cute and functionalβ energy, and weβre gonna read every bit. π
β¨
πΈ SYNOPSIS πΈ
Hereβs the whole vibe in two lines, no cap:
ros install system [system ...]ros install impl[/version] [param ...]
π DESCRIPTION π
systemβ a name specifying a system. πimplβ a name specifying a lisp implementation. β¨
π₯ INSTALLING A LISP IMPLEMENTATION π₯
When the impl or system matches one of the supported implementations, roswell fetches, downloads, and installs it into one of the internal directories managed by roswell (~/.roswell, or ROSWELL_INSTALL_DIR). In order to use the installed implementation, you have to run ros-use(1). π«Ά
For example, this next command downloads the latest sbcl binary from sbcl.org. Heads up though: this may be different from the default binary installed by roswell, called sbcl-bin. And sbcl-bin is a stable and well-tested version of the sbcl binary which is supposed to be a little older than the latest sbcl. So yes, bestie, thereβs a whole distinction there. π
$ ros install sbcl
When invoked without a name, it prints the list of installable implementations. Do not confuse this with ros list installed, which shows the implementations already installed. Periodt. π
Usage: ros install impl [OPTIONS]
For more details on impl specific options, type:
ros help install impl
Candidates impls for installation are:
ecl
sbcl
clisp
ccl-bin
sbcl-bin
The name can be optionally followed by a slash / and a version of the implementation. Like:
$ ros install sbcl/1.2.14
There might be some hidden implementation that are not listed here β they are in the alpha quality, but try the one you like or watch the website (https://github.com/roswell/roswell). Try stuff, bestie:
$ ros install ccl
$ ros install abcl
$ ...
π¦ INSTALLING A QUICKLISP SYSTEM AND THE BUNDLED ROSWELL SCRIPTS π¦
If the specified name does not match any of the implementations, roswell tries to find a quicklisp system of the given name. Cute, right?
$ ros install alexandria
After compiling and loading the system, it funcalls ros:*build-hook* special variable with no argument, if some function is set during the compilation/load. Thatβs the little hook moment. β
When the system comes with a roswell script created by ros-init(1) in the subdirectory roswell, they are installed into ROSWELL_INSTALL_DIR/bin. Setting the path to this directory makes those scripts available from the shell command line. Slay. π
$ ros install qlot
System 'qlot' found. Loading the system..
Processing build-hook..
Found 1 scripts: qlot
Attempting to install the scripts in roswell/ subdirectory of the system...
/home/user/.roswell/bin/qlot
$ qlot
Usage: qlot [install | update | bundle | exec shell-args..]
π SEE ALSO π
Go peek at these other pages, bestie: sbcl(1), ros(1), ros-list(1), ros-init(1). π
π AUTHORS π
Roswell Project Team. They ate. π
Final sign-off: the footer is simply ros-install(1) β no separate source/version or date line here, just the manual name β so bye bestie, go install something iconic πβ¨
π¦ where this page comes from
- alpine 3.24: roswell-doc 24.10.115-r1 Β· MIT
- arch rolling: roswell 26.10.119-1 Β· MIT
- nixos 26.05: roswell 26.02.116
- nixpkgs unstable: roswell 26.10.117
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms