public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: "Björn Raupach" <raupach@e2n.de>,
	"kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: symlink problems with mac os
Date: Sun, 22 Oct 2017 12:54:00 -0000	[thread overview]
Message-ID: <0cfce2d5-3e68-bf23-95c6-f6fc6e717f99@bothner.com> (raw)
In-Reply-To: <7DC458EC-78C0-40B3-871F-5B0E72E43CF5@e2n.de>

On 10/22/2017 05:00 AM, Björn Raupach wrote:
> The readlink version of macOS isn’t the same as GNU/Linux one. The latter version does follow symlinks with -f. The macOS one does not support this feature.
> 
> I stumbled upon this while working on a port for MacPorts<https://www.macports.org>  Should make kawa easier to install and upgrade on macOS. (Of course it is already simple enough being a jar file and such…)

There is a Homebrew port fof Kawa which avoids the problem by patching
bin/kawa before installing it:

https://github.com/Homebrew/homebrew-core/blob/master/Formula/kawa.rb

Another option is to install GNU readlink.

I considered replacing readlink -f by realpath, but as Mac OS doesn't
have readlink either, I don't see how that would help.

We could make the script more complicated, so it can work with plain readlink,
perhaps based on https://github.com/mkropat/sh-realpath/blob/master/realpath.sh .
I'm not thrilled to complicate the script that much, but it may be better
than adding a dependency.

The reason for the readlink to handle the case that you install kawa
as a symlink for example /usr/local/bin/kawa -> /opt/kawa-3.0/bin/kawa .
I think that is useful to support - and it doesn't work without the -f.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2017-10-22 12:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 12:00 Björn Raupach
2017-10-22 12:54 ` Per Bothner [this message]
2017-10-22 13:05   ` Björn Raupach
2017-10-22 17:40     ` Per Bothner
2017-10-22 18:15       ` Björn Raupach
2017-10-22 18:31         ` Per Bothner
2017-10-22 22:10       ` Per Bothner
2017-10-23  6:47         ` Björn Raupach
2017-10-23 16:55           ` Per Bothner
2017-10-30 15:15             ` Björn Raupach

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=0cfce2d5-3e68-bf23-95c6-f6fc6e717f99@bothner.com \
    --to=per@bothner.com \
    --cc=kawa@sourceware.org \
    --cc=raupach@e2n.de \
    /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).