all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: Re: 25/65: gnu: Add sbcl-slime-swank.
Date: Fri, 19 Oct 2018 23:46:40 +0200	[thread overview]
Message-ID: <87a7n9d2yn.fsf@gnu.org> (raw)
In-Reply-To: <20181019155945.4A9D3209DC@vcs0.savannah.gnu.org> (Pierre Neidhardt's message of "Fri, 19 Oct 2018 11:59:45 -0400 (EDT)")

Hi Pierre,

mail@ambrevar.xyz (Pierre Neidhardt) skribis:

> commit c4d4ae1e16254a96caaeb5ccb4486f301ae4f1b7
> Author: Pierre Neidhardt <mail@ambrevar.xyz>
> Date:   Tue Sep 11 22:59:35 2018 +0200
>
>     gnu: Add sbcl-slime-swank.
>     
>     * gnu/packages/lisp.scm (sbcl-slime-swank): New variable.

[...]

> +       (method git-fetch)
> +       (uri (git-reference
> +             ;; (url "https://github.com/slime/slime/")
> +             ;; (commit "841f61467c03dea9f38ff9d5af0e21a8aa29e8f7")
> +             ;; REVIEW: Do we need sionescu's patch to package SWANK?
> +             (url "https://github.com/sionescu/slime/")
> +             ;; (commit "swank-asdf")
> +             (commit "2f7c3fcb3ac7d50d844d5c6ca0e89b52a45e1d3a")))

Leftovers?  :-)

> +    (license (license (list license:gpl2+ license:public-domain)))))

For the record this typo made it impossible to build Guix (“license:
unbound variable”).  This was easily fixed in
0ee6692a63538e874ba0b4d85584a4a73b75367c so no big deal, though make
sure to run “make” before “git push” next time.

Thank you for all the Common Lisp packages!

Ludo’.

       reply	other threads:[~2018-10-19 21:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181019155940.19485.23687@vcs0.savannah.gnu.org>
     [not found] ` <20181019155945.4A9D3209DC@vcs0.savannah.gnu.org>
2018-10-19 21:46   ` Ludovic Courtès [this message]
2018-10-19 22:23     ` 25/65: gnu: Add sbcl-slime-swank Pierre Neidhardt
2018-10-20 10:10       ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7n9d2yn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.