Sujet : Re: releasing a first quicklisp package
De : wagnes (at) *nospam* jemoni.to (Wolfgang Agnes)
Groupes : comp.lang.lispDate : 31. Oct 2024, 12:17:05
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <87jzdo4j4e.fsf@jemoni.to>
References : 1 2
Ralph Schleicher <rs+
usenet@ralph-schleicher.de> writes:
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?
Yes, I do.
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?
I could have people clone a git repository and then say "make install".
Something like that is what you have in mind? I think that would work
well. But I also want to release a quicklisp package because I
primarily have Common Lisp developers in mind.
Otherwise, ever though about shipping a pre-built standalone
executable file instead?
As a second step---once I have a homepage set up, for instance. I'd
build executables for popular systems.