Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <5.1.0.14.0.20010701101003.034141f0@rufus.swip.net>
X-Sender: mr58976 AT rufus DOT swip DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sun, 01 Jul 2001 10:18:27 +0200
To: cygwin AT cygwin DOT com
From: Jens Yllman <jens DOT yllman AT swipnet DOT se>
Subject: Symbolic links.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

  Hi,

  setup.exe uses the old symbolic links when it installs packages. Is this 
realy correct?

  Then I noticed some talk about .lnk here on the list. .lnk files created 
from windows may contain alot more information then a .lnk file created by 
cygwin as a symbolic link.

  I think that a .lnk file created by windows can not be treated as a 
symbolic link in cygwin. At least not in the archiving sence.

  You might say that why archive windows files with a UNIX tool? At the 
moment I'm spending alot of time trying to make may programs compile with 
both Borland C++, Visual C++ and gcc. And those project may contain .lnk 
files that are not symbolic links in the cygwin sence. And should be 
presesrved when archived.

  So using the .lnk for symbolic links may be a bad choose. Using a 
fileformat that can contain/handle more then one thing is not a good thing 
if used in a system for only one thing.

  These are just my thougts. I've not read through all the posts on this 
list. So I might state something that is already clear.

  Jens Yllman



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/