My plan for the installation of the service is to write a program that invokes quicklisp to download the packages and then create all the files necessary to run the service in a certain installation directly. In
other words, the sysadmin would install and have the service ready to
run with a single command. The procedure that would do such preparation would be in the Common Lisp package that quicklisp will download and
install.
Wolfgang Agnes <wagnes@jemoni.to> writes:
My plan for the installation of the service is to write a program that
invokes quicklisp to download the packages and then create all the files
necessary to run the service in a certain installation directly. In
other words, the sysadmin would install and have the service ready to
run with a single command. The procedure that would do such preparation
would be in the Common Lisp package that quicklisp will download and
install.
So you presume the target system has a properly configured Common
Lisp system installed?
If so, why don't you just ship the source code together with the
installation script so that you do not have to download anything?
Otherwise, ever though about shipping a pre-built standalone
executable file instead?
But I also want to release a quicklisp package because I
primarily have Common Lisp developers in mind.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 403 |
Nodes: | 16 (2 / 14) |
Uptime: | 43:32:31 |
Calls: | 8,407 |
Calls today: | 2 |
Files: | 13,171 |
Messages: | 5,905,025 |