From: Pierre Neidhardt <mail@ambrevar.xyz>
To: jgart@dismail.de, 51903@debbugs.gnu.org
Cc: jgart <jgart@dismail.de>
Subject: [bug#51903] [PATCH] gnu: Add cl-cmn.
Date: Wed, 17 Nov 2021 08:49:48 +0100 [thread overview]
Message-ID: <871r3fte5f.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20211117015205.19233-1-jgart@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hi,
1. I believe you should place the lib in lisp-xyz.scm.
2. License is llgpl.
3. Then use the asdf-build-system/sbcl.
See the other sbcl- packages for reference.
Then define the cl- package with
--8<---------------cut here---------------start------------->8---
(define-public cl-cmn
(sbcl-package->cl-source-package sbcl-cmn))
--8<---------------cut here---------------end--------------->8---
4. Since there are no version numbers, maybe use the date of the last
HISTORY.cmn entry, that is, 2016.8.17.
Hope that helps!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2021-11-17 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 1:52 [bug#51903] [PATCH] gnu: Add cl-cmn jgart via Guix-patches via
2021-11-17 7:49 ` Pierre Neidhardt [this message]
2021-11-17 8:50 ` jgart via Guix-patches via
2021-11-17 9:24 ` Pierre Neidhardt
2021-11-17 8:55 ` [bug#51903] [PATCH v2] " jgart via Guix-patches via
2021-11-17 10:39 ` [bug#51903] cmn license etc bil
2021-11-21 12:51 ` Guillaume Le Vaillant
2021-11-21 14:16 ` bil
2021-11-21 16:20 ` Guillaume Le Vaillant
2021-11-21 17:45 ` bil
2021-11-21 17:54 ` Guillaume Le Vaillant
2021-11-21 19:22 ` bil
2021-11-22 0:30 ` jgart via Guix-patches via
2021-11-22 10:10 ` Guillaume Le Vaillant
2021-11-22 14:13 ` bil
2021-11-22 18:35 ` [bug#51903] [PATCH v3] gnu: Add cl-cmn jgart via Guix-patches via
2021-11-22 19:45 ` bug#51903: " Guillaume Le Vaillant
2021-11-22 20:11 ` [bug#51903] " jgart via Guix-patches via
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=871r3fte5f.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=51903@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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).