From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Guix Devel <guix-devel@gnu.org>
Subject: Common Lisp packaging conventions
Date: Thu, 16 Jan 2025 17:12:28 +0100 [thread overview]
Message-ID: <m1zfjq91qr.fsf@fastmail.net> (raw)
Hi everyone,
I have packaged but not yet submitted CommonDoc
(https://github.com/CommonDoc/common-doc) for Guix. What has kept me so
far from submitting it is an uncertainty about conventions for
packaging Common Lisp code.
The repository cited above contains multiple Lisp systems: a core system
plus optional add-ons. There is a single test suite for all of the code.
I see three ways to package this for Guix:
1. A single package with a single output for the whole
repository. Disadvantage: code and, more importantly, dependencies
that most users don't need.
2. A single package for the repository, with the add-ons placed in
different outputs. Disadvantage: the add-ons are more difficult
to discover and use.
3. Separate packages for each add-on. Disadvantage: requires some
heavy patching, in particular for the test suite.
Which option is the Guix Way (TM) ?
Cheers,
Konrad.
next reply other threads:[~2025-01-16 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 16:12 Konrad Hinsen [this message]
2025-01-18 12:50 ` Common Lisp packaging conventions Guillaume Le Vaillant
2025-01-19 20:04 ` Konrad Hinsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1zfjq91qr.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).