From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-6373-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 1419 invoked from network); 31 May 1999 06:42:23 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 31 May 1999 06:42:23 -0000
Received: (qmail 27497 invoked by alias); 31 May 1999 06:42:14 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 6373
Received: (qmail 27490 invoked from network); 31 May 1999 06:42:14 -0000
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
        "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Re: pws-19: compinstall should build absolute paths
Date: Mon, 31 May 1999 10:41:12 +0400
Message-ID: <000201beab30$9326dc50$21c9ca95@mow.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <990529103000.ZM7564@candle.brasslantern.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300


> I'm not entirely certain that using absolute paths is the best thing here;
> I worry about things like NFS filesystems that don't have the same mount
> points everywhere.  But I can't think of anything better.
>

I am not sure, that compinstall can take in account all possible
configurations. In case of NFS mounted HOME (probably, the most common
case) - I always used ``~/...'' - that should be portable even if HOME
changes.

> +if [[ ${~_ci_fdir} != /* ]]; then
> +  _ci_fdir=$(cd $_ci_fdir;builtin pwd)
> +fi
>
>  # Check if this is in fpath already, else put it there (with ~'s
> expanded).
>  _ci_f=${~_ci_fdir}
>

Ehh ... but at this point _ci_fdir is an absolute path ... and starts with
``/'' ... so _ci_f is set to some directory in HOME instead to _ci_fdir, is
not it?

/andrej