Currently deployment of a development environment is awkwardly handled through the deploy.sh script. Instead a separate quicklisp dist should be used to provide all necessary libraries in a more up-to-date manner than QL. This would integrate better with the general CL ecosystem and would avoid platform-compatibility issues of shell scripts.
Deployment of Radiance onto end-user machines also needs to be thought out. Having them set up a CL environment is not an acceptable idea. It needs to be packaged or automatically deployed in some way. Developers of Radiance frameworks or components also need a way to utilise this thing to create their own, custom deployments.
Currently deployment of a development environment is awkwardly handled through the
deploy.sh
script. Instead a separate quicklisp dist should be used to provide all necessary libraries in a more up-to-date manner than QL. This would integrate better with the general CL ecosystem and would avoid platform-compatibility issues of shell scripts.Deployment of Radiance onto end-user machines also needs to be thought out. Having them set up a CL environment is not an acceptable idea. It needs to be packaged or automatically deployed in some way. Developers of Radiance frameworks or components also need a way to utilise this thing to create their own, custom deployments.