From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>,
kawa mailing list <kawa@sourceware.org>
Subject: Re: Kawa 2.2 broken on OSX when using Homebrew
Date: Wed, 28 Dec 2016 08:50:00 -0000 [thread overview]
Message-ID: <7d6889b8-246b-b530-a31d-279c3bf5a0a9@bothner.com> (raw)
In-Reply-To: <CABgWrqqrJ0NKxqY8NeiSp=_-quiAUTOHz8WJUma8dgmbp_NssA@mail.gmail.com>
On 12/28/2016 08:53 AM, Duncan Mak wrote:
> Hello Per,
>
> I think the changes to the Kawa distribution in 2.2 are not properly
> reflected in the packaging on OSX by the Homebrew people.
That is plausible/ Kawa 2.2 switched to a new way of making
binary releases, with the jline3 and domterm libraries (as well
as the documentation) bundled. You will have to evaluate if that
makes sense for homebrew. If so you probably the kawa-$(VERSION).zip
rule, or something similar. For most platforms it should just
work to unzip the resulting zip, and optionally create suitable
symlinks and/or adjust the environment.
I want to release a 2.3 release ASAP. This is mainly to update
the documentation and website to refer to git rather than Subversion.
If you find any Mac/Homebrew problems (soon) we can also include those.
> Currently, it's built using this Formula -
> https://github.com/Homebrew/homebrew-core/blob/master/Formula/kawa.rb
The main issue I can see whether you want to bundle JLine3 and DomTerm,
and it so how you handle the dependencies.
> I noticed that the readline front-end is not included,
The readline front-end is deprecated - I use the JLine3 front.end now.
> and I'm also not able to import SRFIs.
>
> duncan@furigana:~$ brew install kawa
> ==> Downloading
> https://homebrew.bintray.com/bottles/kawa-2.2.el_capitan.bottle.tar.gz
> ==> Pouring kawa-2.2.el_capitan.bottle.tar.gz
> 🺠/usr/local/Cellar/kawa/2.2: 19 files, 3.5M
>
> duncan@furigana:~$ kawa
> #|kawa:1|# (import (srfi 1))
> /dev/stdin:1:9: unknown library (srfi 1)
> #|kawa:2|# ^A ;; this gets printed instead of cursor movement
Nothing comes to mind ...
> I have time this week to go fix it, could you review the build formula
> and let me know if there's anything wrong with it? I think it might be
> missing some configure flags.
See what kawa-#(CRESION).zip make rule does.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-12-28 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 7:54 Duncan Mak
2016-12-28 8:50 ` Per Bothner [this message]
2016-12-29 20:41 ` Duncan Mak
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=7d6889b8-246b-b530-a31d-279c3bf5a0a9@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.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.
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).