public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: "Björn Raupach" <raupach@me.com>
Cc: "kawa@sourceware.org" <kawa@sourceware.org>
Subject: Re: symlink problems with mac os
Date: Mon, 23 Oct 2017 16:55:00 -0000	[thread overview]
Message-ID: <b809abfd-1062-5290-31d0-3790a6f71705@bothner.com> (raw)
In-Reply-To: <4A6C2C7B-39EE-4D32-9A2D-D715CFD62D3B@me.com>

On 10/22/2017 11:47 PM, Björn Raupach wrote:

> Thanks for spending time on this. Like I said it is really a minor issue.

True. Regardless, I prefer a cleaner/simpler file layout that minimizes symlinks.
If that can avoid a problem on Mac so much the better.

> Unfortunately I couldn’t make it work. Might be a misunderstanding on my part.

I forgot about this: there is a both a share/kawa/bin/kawa, and a bin/kawa
that is a link to the latter.  That seems ugly.  The reason is so that the
kawa script can just look for ../kawa/lib/kawa.jar, regardless of whether we:
(1) run-in-place in the build directory,
(2) run installed files (result of 'make install'), or
(3) run from an unzipped kawa.zip binary distribution.

I think there are better ways to solve this "multi-mode problem" - one is
for 'make install' to make a one-line patch to the kawa script as it is installed.

-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2017-10-23 16:55 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
2017-10-22 22:10       ` Per Bothner
2017-10-23  6:47         ` Björn Raupach
2017-10-23 16:55           ` Per Bothner [this message]
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=b809abfd-1062-5290-31d0-3790a6f71705@bothner.com \
    --to=per@bothner.com \
    --cc=kawa@sourceware.org \
    --cc=raupach@me.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).