public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: kawa-3.1.1 released
Date: Fri, 17 Jan 2020 18:31:00 -0000	[thread overview]
Message-ID: <CABgWrqoaSQLRfaUyw8cDKQVrub15kHg-cnz510AS9R_3i4kwag@mail.gmail.com> (raw)
In-Reply-To: <e26fb7a5-8daf-49c3-da68-2828a025613b@bothner.com>

On Fri, Jan 17, 2020 at 1:33 AM Per Bothner <per@bothner.com> wrote:
>
> I'm not sure whether you mean this is a bug in kawa 3.1.1 (as
> released) or in how Homebrew installs it?
>
> There are multiple ways one could "install" Kawa.  One specific
> way that I intend to support is that you could just unzip kawa-VERSION.zip
> into a location, optionally and then set up a bunch of symlinks.  For example:
>
> cd /usr/local/Cellar
> unzip kawa-VERSION.zip
> # Optionally: mkdir -p kawa && mv kawa-VERSION to kawa/VERSION
> cd /path-to-homebew-bin/ && ln -s /usr/local/Cellar/kawa-VERSION/bin/kawa kawa

The bug is in my PR, which is what Homebrew calls the Formula. I don't
think the bug is in kawa 3.1.1.

My PR with just the version bump has just been accepted.

I'll try to send another PR to Homebrew to properly copy the doc
directory with the epub file to the right place so that the
browse-manual feature would work.

Thanks!

-- 
Duncan.

  reply	other threads:[~2020-01-17 18:31 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
2020-01-17  6:34       ` Per Bothner
2020-01-17 18:31         ` Duncan Mak [this message]
     [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=CABgWrqoaSQLRfaUyw8cDKQVrub15kHg-cnz510AS9R_3i4kwag@mail.gmail.com \
    --to=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /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).