| Deutsch English Français Italiano |
|
<86wmhoft7s.fsf@ralph-schleicher.de> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Ralph Schleicher <rs+usenet@ralph-schleicher.de> Newsgroups: comp.lang.lisp Subject: Re: releasing a first quicklisp package Date: Thu, 31 Oct 2024 11:43:35 +0100 Organization: Ralph Schleicher Lines: 18 Message-ID: <86wmhoft7s.fsf@ralph-schleicher.de> References: <8734kojfx9.fsf@jemoni.to> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Thu, 31 Oct 2024 12:08:04 +0100 (CET) Injection-Info: dont-email.me; posting-host="7295fd32364d8b73ca257df432edb9a6"; logging-data="2810616"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/tGHPDMOfLTKhV8jVypVq8EMdyLucPwzw=" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:aXIPOdWiHhCM+FWJ8Drj/2VTU9k= sha1:TZYWM1h2l4/9CFMxkwUQI8gsbvs= Bytes: 1782 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? -- Ralph