From: Duncan Mak <duncanmak@gmail.com>
To: kawa mailing list <kawa@sourceware.org>
Subject: Re: kawa-3.1.1 released
Date: Fri, 17 Jan 2020 03:33:00 -0000 [thread overview]
Message-ID: <CABgWrqpuTLq3UyLrQ+vgUiP5BJf=Tb9JCQKGGm2ZnDXh7s96iA@mail.gmail.com> (raw)
In-Reply-To: <CABgWrqoZ=uOzARP2XygyYFRK5U=4JStQ7-ueKKs9fa-nzYg_4w@mail.gmail.com>
Ahh, I just checked, I can look into updating the PR to fix the follow
issue this weekend:
As a follow up, I can make a patch later on to fix this:
$ kawa --browse-manual=javafx
kawa: --browse-manual=javafx failed:
/usr/local/Cellar/kawa/3.1.1/libexec/doc/kawa-manual.epub does not
exist
Duncan.
On Thu, Jan 16, 2020 at 10:29 PM Duncan Mak <duncanmak@gmail.com> wrote:
>
> I have submitted a PR to update Homebrew to include Kawa 3.1.1:
>
> https://github.com/Homebrew/homebrew-core/pull/49108
>
>
> Duncan.
>
>
> On Thu, Jan 16, 2020 at 4:22 PM ian <sibian0218@gmail.com> wrote:
> >
> > Hi,
> >
> > OK Per, I'll check this ASAP.
> >
> > And, yes, I experienced problems trying to use the browse-manual....
> >
> > FYI I'm currently on an old i386 under Buster GNU/Linux.
> >
> > Keep you informed.
> >
> >
> > Kindly Regards.
> >
> > ian
> >
> > Le 16/01/2020 à 22:19, Per Bothner a écrit :
> > > Kawa 3.1.1 is now available.
> > >
> > > No real new features since 3.1 but I fixed various packaging bugs
> > > (including
> > > the missing kawa shell script in the zip binary distribution).
> > > I also fixed some problems using the --browse-manual option,
> > > which now defaults to creating a JavaFX window (when JavaFX is
> > > available).
> > >
> > > https://www.gnu.org/software/kawa/news.html
> > >
> > > The release is available from the usual places:
> > >
> > > ftp://ftp.gnu.org/pub/gnu/kawa/kawa-3.1.1.tar.gz (Source release)
> > > ftp://ftp.gnu.org/pub/gnu/kawa/kawa-3.1.1.zip (Binary release)
> > >
> > > https://www.gnu.org/software/kawa/index.html (Home page and general
> > > documentation)
> > --
> > -- ian@sibian.fr
> > -- Développeur compulsif
>
>
>
> --
> Duncan.
--
Duncan.
next prev parent reply other threads:[~2020-01-17 3:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 21:19 Per Bothner
2020-01-16 21:22 ` ian
2020-01-17 3:29 ` Duncan Mak
2020-01-17 3:33 ` Duncan Mak [this message]
2020-01-17 6:34 ` Per Bothner
2020-01-17 18:31 ` Duncan Mak
[not found] ` <CABgWrqoT2yHUWcDcJ3fSixH9QUcgOCDkUPLBZEcA6NajN2mo-w@mail.gmail.com>
2020-01-18 0:33 ` Per Bothner
2020-02-28 21:22 ` Lassi Kortela
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='CABgWrqpuTLq3UyLrQ+vgUiP5BJf=Tb9JCQKGGm2ZnDXh7s96iA@mail.gmail.com' \
--to=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).