all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35082@debbugs.gnu.org
Subject: [bug#35082] [PATCH] gnu: Add kawa.
Date: Thu, 04 Apr 2019 10:10:45 +0200	[thread overview]
Message-ID: <87mul6xkai.fsf@elephly.net> (raw)
In-Reply-To: <87y34qtcxv.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hi again,
>
> Carlo Zancanaro <carlo@zancanaro.id.au> skribis:
>
>> --- a/gnu/packages/scheme.scm
>> +++ b/gnu/packages/scheme.scm
>> @@ -31,7 +31,7 @@
>>    #:use-module (gnu packages)
>>    #:use-module ((guix licenses)
>>                  #:select (gpl2+ lgpl2.0+ lgpl2.1+ lgpl3+ asl2.0 bsd-3
>> -                          cc-by-sa4.0 non-copyleft))
>> +                          cc-by-sa4.0 non-copyleft expat))
>>    #:use-module (guix packages)
>>    #:use-module (guix download)
>>    #:use-module (guix git-download)
>> @@ -69,6 +69,7 @@
>>    #:use-module (gnu packages tls)
>>    #:use-module (gnu packages gl)
>>    #:use-module (gnu packages libedit)
>> +  #:use-module (gnu packages java)
>
> It just occurred to me that this new dependency on java.scm is probably
> not desirable since it pulls in a lot of additional stuff.  I think we
> should instead move Kawa to java.scm.  WDYT?

…or even to kawa.scm, just as we have clojure.scm.  I’ve been meaning to
move everything but the JDK bootstrap out of java.scm.

--
Ricardo

  reply	other threads:[~2019-04-04  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 13:16 [bug#35082] [PATCH] gnu: Add kawa Carlo Zancanaro
2019-04-03 20:30 ` Ludovic Courtès
2019-04-04  0:33   ` Carlo Zancanaro
2019-04-04  8:01     ` Ludovic Courtès
2019-04-04  8:03     ` Ludovic Courtès
2019-04-04  8:10       ` Ricardo Wurmus [this message]
2019-06-13 11:02         ` bug#35082: " 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=87mul6xkai.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=35082@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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.