From: "Björn Raupach" <raupach@e2n.de>
To: Per Bothner <per@bothner.com>
Cc: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: symlink problems with mac os
Date: Sun, 22 Oct 2017 18:15:00 -0000 [thread overview]
Message-ID: <9DD66D7B-E0BE-441F-BD51-3F255A505F00@e2n.de> (raw)
In-Reply-To: <9a15e187-6123-2c5a-181b-e4ebb9ac0dc8@bothner.com>
> On 22. Oct 2017, at 19:40, Per Bothner <per@bothner.com> wrote:
>
> On 10/22/2017 06:04 AM, Björn Raupach wrote:
>
>> 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
>> Agreed. I would do a patch like this in MacPorts, too. Was just raising awareness of this minor issue if it was unnoticed before.
>
> I've been vaguely aware of it.
>
>> 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.
>
> On second though that use-case can be handled just as well with creating
> an executable file /usr/local/bin/kawa containing:
>
> exec /opt/kawa-3.0/bin/kawa "$@“
Not sure about this. Probably wouldn’t help my case. What if I don’t install in /opt/kawa-3.0?
>
> However, when doing a source build, and then executing from the build
> directory (as the test-suite does) still has to traverse a symlink,
> as configure creates a symlink from kawa.sh to kawa.sh.in.
>
>> The maven snippet above handles that case. I can link a link and still get maven to run. Would make it portable and doesn’t need any dependency.
>
> It would slow start up a little bit.
I don’t think it matters much. Slow start is already caused by starting a JVM. Starting chicken scheme or mit scheme feels more snappier. But we are talking felt milliseconds here. Compared to other programs kawa already starts fast.
>
>> Looking for patches? I have time to look at that and now I am curious enough to try and solve this. ;)
>
> I think I want to leave kawa.sh.in as-is, but have configure
> create kawa instead of kawa.sh. That way we don't need a symlink in the normal case.
> I'm trying this out now.
Alright. I will still try to copy the plain bash approach in your startup script. Just to see if I can get it to run.
Happy Sunday
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2017-10-22 18:15 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
2017-10-22 13:05 ` Björn Raupach
2017-10-22 17:40 ` Per Bothner
2017-10-22 18:15 ` Björn Raupach [this message]
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=9DD66D7B-E0BE-441F-BD51-3F255A505F00@e2n.de \
--to=raupach@e2n.de \
--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).