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: Tue, 02 Oct 2018 12:24:29 +0200 [thread overview]
Message-ID: <878t3gwsrm.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20181002045531.78223c72@mailservices.uwaterloo.ca>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
> It'd be nice to have an importer. Maybe we can use Nix's work to
> reduce the amount of investigation needed to get there.
Absolutely. ASDF is good enough that the vast majority of CL libraries can be
packaged without an itch.
If we could use Quicklisp or
http://quickdocs.org/
to write a recursive importer, we could get programs like Next browser packaged
in one go but for a couple of tweaks for the 2-3 odd packages.
Let me know if you want to work on this, otherwise I'll give it a shot.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-10-02 10:25 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
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 [this message]
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=878t3gwsrm.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).