* Common Lisp packaging conventions
@ 2025-01-16 16:12 Konrad Hinsen
2025-01-18 12:50 ` Guillaume Le Vaillant
0 siblings, 1 reply; 3+ messages in thread
From: Konrad Hinsen @ 2025-01-16 16:12 UTC (permalink / raw)
To: Guix Devel
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Common Lisp packaging conventions
2025-01-16 16:12 Common Lisp packaging conventions Konrad Hinsen
@ 2025-01-18 12:50 ` Guillaume Le Vaillant
2025-01-19 20:04 ` Konrad Hinsen
0 siblings, 1 reply; 3+ messages in thread
From: Guillaume Le Vaillant @ 2025-01-18 12:50 UTC (permalink / raw)
To: Konrad Hinsen; +Cc: Guix Devel
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> 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.
Hi.
Usually we make a single package and declare which ASDF systems to
compile with the 'asd-systems' keyword in the arguments field (so the
option 1 in your list).
However if an add-on system is really huge compared to the basic system,
putting it in its own package is not forbidden.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Common Lisp packaging conventions
2025-01-18 12:50 ` Guillaume Le Vaillant
@ 2025-01-19 20:04 ` Konrad Hinsen
0 siblings, 0 replies; 3+ messages in thread
From: Konrad Hinsen @ 2025-01-19 20:04 UTC (permalink / raw)
To: Guillaume Le Vaillant; +Cc: Guix Devel
Hi Guillaume,
> Usually we make a single package and declare which ASDF systems to
> compile with the 'asd-systems' keyword in the arguments field (so the
> option 1 in your list).
Thanks for your input! Since that's the easiest solution for me as a
packager, I won't complain :-)
> However if an add-on system is really huge compared to the basic system,
> putting it in its own package is not forbidden.
OK. I will consider this for the two add-ons that require larger
dependencies (Gnuplot and Graphviz).
Cheers,
Konrad
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-01-19 20:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-16 16:12 Common Lisp packaging conventions Konrad Hinsen
2025-01-18 12:50 ` Guillaume Le Vaillant
2025-01-19 20:04 ` Konrad Hinsen
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).