common-lisp/roswell.roswell
1
0
Fork 0
mirror of https://github.com/roswell/roswell.git synced 2026-09-10 07:16:17 -04:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
Page: Policy on how Roswell affects or manipulates your system
Pages
1. Installation Advanced scripting Basic Usage Building images and executables Circle CI Coveralls FAQ GitHub Actions Home How is Roswell different How to distribute your software, not library, on Quicklisp ala python pip How to setup a lisp dev environment on windows with Roswell Initial Recommended Setup Installation List of Roswell Installable Scripts Listing various resources Local installation Policy on how Roswell affects or manipulates your system Practical Usecases Reducing Startup Time Release Roswell Roswell as a Scripting Environment Roswell as a Testing Environment Roswell as an implementation manager Roswell in Virtual Environments Set up guide for Anaconda virtual env Support New implementation Travis CI Upgrading Roswell ros template
1 Policy on how Roswell affects or manipulates your system
Masataro Asai edited this page 2018-01-19 20:17:53 +09:00

Roswell keeps its effect on the system to the minimum.

Installing roswell on linux causes the core C runtime (ros binary) in /usr/local/bin/ and a few lisp files under /usr/local/etc/roswell. They are completely safe to remove once you decide to remove roswell. You can optionally change this installation directory by ./configure --prefix=/path/. See Local installation.

Roswell DOES NOT use this directory for its runtime operation (subcommands like ros install sbcl). Files downloaded/created/manipulated by Roswell are kept under ~/.roswell directory. It is completely safe to remove this directory without affect the integrity of the system, nor roswell itself. Removing this directory means resetting Roswell to the blank state, just like removing ~/.mozilla for firefox which removes all of your preferences/history/plugins.

Quicklisp, ASDF, or Quicklisp libraries installed by Roswell does not affect, nor is affected by, the Quicklisp, ASDF, or the libraries that you installed manually. Roswell downloads and keeps them separately under ~/.roswell.

Implementations installed by Roswell does not affect, nor is affected by, the implementations already installed on the system. However, roswell is able to use those systems by ros use <IMPL>/system (e.g. ros use sbcl/system) or ros -L <IMPL>/system ... which uses the binary visible from PATH.

Roswell does not write to the system configuration files nor user configuration files outside roswell, such as .profile, .bashrc, .emacs or .sbclrc. Nor does Roswell magically alter the environment variables like PATH.

Home

Getting started / Tutorials

Advanced Installation

Roswell as a scripting environment

Roswell as an implementation manager

Roswell as a Testing Environment

Distributing applications

FAQ

For Developers/Maintainers