From: Per Bothner <per@bothner.com>
To: "Björn Raupach" <raupach@e2n.de>
Cc: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: symlink problems with mac os
Date: Sun, 22 Oct 2017 18:31:00 -0000 [thread overview]
Message-ID: <ca1360c4-2c9c-b8a9-424c-0694779ed41f@bothner.com> (raw)
In-Reply-To: <9DD66D7B-E0BE-441F-BD51-3F255A505F00@e2n.de>
On 10/22/2017 11:15 AM, Björn Raupach wrote:
>> On 22. Oct 2017, at 19:40, Per Bothner <per@bothner.com> wrote:
>>> 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?
That is just an example. I'm talking about either
(a) building from source (and then running in-place without doing 'make install') or
(b) unzip the binary distribution in some directory - for example /opt/kawa-3.0.
After that you might want to put 'kawa' in your PATH. Instead if adding another entry
to your PATH variable, you can either:
(1) create a 'kawa' symlink from a directory in your PATH to (for example)
/opt/kawa-3.0/bin/kawa, or
(2) create a small shell file containing 'exec /opt/kawa-3.0/bin/kawa "$@â'
in a directory in your path.
Option (1) requires 'readlink -f' to work - but option (2) doesn't.
(Assuming I fix thing so $builddir/bin/kawa is no longer a symlink.)
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2017-10-22 18:31 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
2017-10-22 18:31 ` Per Bothner [this message]
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=ca1360c4-2c9c-b8a9-424c-0694779ed41f@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).