From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Andy Patterson <ajpatter@uwaterloo.ca>
Cc: 32770@debbugs.gnu.org
Subject: bug#32770: Packaging SLIME/SWANK as Common Lisp library
Date: Sun, 30 Sep 2018 23:46:08 +0200 [thread overview]
Message-ID: <87k1n2wten.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87lg7iwu9i.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Also see
https://github.com/quicklisp/quicklisp-projects/issues/1561
There are some interesting links, mostly about the Nix system. See the
https://github.com/NixOS/nixpkgs/blob/5048b0d1f9e908665a01c35f49b2d9816128e089/pkgs/development/lisp-modules/quicklisp-to-nix-output/swank.nix
file: I think it would have given us a clear hint with ~asdFilesToKeep =
["swank.asd"];~, had we looked at Nix before.
I haven't looked to closely into what else Nix is doing to package Common Lisp,
but it seems rather complete. Any good idea we could borrow, Andy?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-09-30 21:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 7:19 bug#32770: Packaging SLIME/SWANK as Common Lisp library Pierre Neidhardt
2018-09-29 19:16 ` Andy Patterson
2018-09-30 21:27 ` Pierre Neidhardt
2018-09-30 21:46 ` Pierre Neidhardt [this message]
2018-10-01 13:53 ` Pierre Neidhardt
2018-10-02 8:38 ` Andy Patterson
2018-10-02 8:55 ` Andy Patterson
2018-10-02 10:24 ` Pierre Neidhardt
2018-10-03 5:22 ` Andy Patterson
2018-10-03 18:34 ` Pierre Neidhardt
2018-10-03 19:48 ` Pierre Neidhardt
2018-10-04 5:03 ` Andy Patterson
2018-10-04 8:37 ` Pierre Neidhardt
2018-10-04 18:08 ` Ricardo Wurmus
2018-10-04 20:38 ` Pierre Neidhardt
2019-10-06 11:53 ` Pierre Neidhardt
2018-10-05 4:56 ` Andy Patterson
2018-10-05 8:28 ` Pierre Neidhardt
2018-10-05 11:44 ` Ricardo Wurmus
2018-10-05 13:30 ` Pierre Neidhardt
2018-10-10 5:54 ` Andy Patterson
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=87k1n2wten.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=32770@debbugs.gnu.org \
--cc=ajpatter@uwaterloo.ca \
/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).