Message-Id:	<200504060757.j367uvLk020824@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Reply-To:	<fergus AT bonhard DOT uklinux DOT net>
From:	<fergus AT bonhard DOT uklinux DOT net>
To:	"'Eric Blake'" <ericblake AT comcast DOT net>
Cc:	<cygwin AT cygwin DOT com>
Subject:	RE: Unusual new look to symlinks to executables
Date:	Wed, 6 Apr 2005 08:54:51 +0100
MIME-Version:	1.0
In-Reply-To:	<040520052315.15459.42531C000005BAFE00003C6322069984990A050E040D0C079D0A@comcast.net>
X-UoD-Spam-Score:	-4.7 (----)
X-UoD-Spam-Report:	-------------------------------------------------- This message has been scanned by a SpamAssassin installation on the spam checking server hughtoo at the University of Dundee. Content analysis details: (-4.7 hits, 5.0 required) 0.2 NO_REAL_NAME From: does not include a real name -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000]
X-UoD-Scan-Signature:	c603c42f4d7f7ea6a8916c62997d080c
Note-from-DJ:	This may be spam

Thank you for responding so quickly and so fully.

> Also, did you upgrade to cygwin 1.5.14 at the same time?
> It might be a change in the cygwin path handling.

Not at the same time, but it may be that this was the first time I used the
"link-checking script" since upgrading to 1.5.14. Certainly that struck me
as a possible cause for the changed behaviour, but it also appeared to me
that all the altered links were related to coreutils and tetex, which is why
I drew the conclusions that I did. 

> By default, ls does not display just a filename and its link contents.

I was using ls -alF but edited the output in my email to just show filename
and link contents.

>> So perhaps it is accidental, and should not have happened?

> It certainly was not intentional.
> It is tricky to get both ln(1) and ls(1) to handle implicit .exe magic
correctly,
> and I may need to release a new coreutils that makes it more consistent in
the future.

Thanks for explaining everything so fully. The reason for using my
link-checking script is that it pipes its output to other scripts, that then
change all symlinks created as Windows +S system files to Windows +R *.lnk
files, for later copying to CD. It was the "change" scripts that were broken
as a consequence of the phenomenon I have described.

It seems to me that it will be unduly optimistic to assume future
consistency in the Cygwin provision -- as in links always being of the form
execlink -> execname.exe -- and that I have been remarkably fortunate to
find such consistency up to now; and that I will need to alter my scripts to
cover the additional possibility execlink -> execname.

Thanks again for all your help.

Fergus


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -