Path: ...!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Wolfgang Agnes <wagnes@jemoni.to>
Newsgroups: comp.lang.lisp
Subject: releasing a first quicklisp package
Date: Tue, 22 Oct 2024 12:49:54 -0300
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <8734kojfx9.fsf@jemoni.to>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Tue, 22 Oct 2024 17:50:00 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="2b8d20cd3ccd2af42b0dc14dc0fc2926";
	logging-data="1635607"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Flg3U+B8JfoZUTCV8bdmx0yfblFXPg+M="
Cancel-Lock: sha1:VMacwfsNokpCVaA/RwJg1hNc/T4=
	sha1:J3mB7+l6gQwDjzp4q1C5xCY/s3s=
Bytes: 2087

I wrote a couple of Common Lisp packages, one very small and a larger
one that contains procedures for an Internet service.  How should I
organize them to be in a quicklisp package?  Should I make two quicklisp
packages?  (I'd say no---one is too small to matter as a package.)

Is it okay for two packages to form a single quicklisp package?  How do
you guys decide such things?

Also, the larger package is not quite a package---it's really just the
set of procedures that I need for the service.  It's not likely that
someone would use these packages except to run the Internet service.  In
other words, I intend to use quicklisp as a way to easily install the
software.  Is that okay?

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.

I'd appreciate hearing the best practices.  Thanks!