ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2001/11/10/23:28:57

Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3BEDFE95.3000200@ece.gatech.edu>
Date: Sat, 10 Nov 2001 23:29:09 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: symlinks
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F28B AT itdomain002 DOT itdomain DOT net DOT au>

Robert Collins wrote:

> When extracting tarballs, should setup create 'native' symlinks or magic
> cookie symlinks?

I thought the magic cookie (!<symlink>target) symlinks were deprecated. 
Currently, "ln -s" makes "special" .lnk shortcuts; I think setup should do 
the same -- there should be no difference between the following scenarios:

1) install the "official" foo package using setup
2) download foo-src and do a "make install"

In both cases, any symlinks created should be the same -- and that means 
.lnk.  (Currently, it *appears* that this is not the case: 2) creates .lnk 
symlinks, but 1) makes magic cookie symlinks)


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019