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
Delivered-To:	fixup-cygwin AT cygwin DOT com@fixme
From:	"Paul Garceau" <pgarceau AT qwest DOT net>
Organization:	New Dawn Productions
To:	cygwin AT cygwin DOT com
Date:	Sat, 24 Feb 2001 16:22:03 -0800
Subject:	Re: [ANNOUNCEMENT]: Important change to symbolic link functionali ty
Reply-to:	Paul Garceau <pgarceau AT qwest DOT net>
Message-ID:	<3A97DFAB.22135.A32889@localhost>
In-reply-to:	<20010224183009.B6893@redhat.com>
References:	<20010222215326 DOT A908 AT cygbert DOT vinschen DOT de>; from cygwin AT cygwin DOT com on Thu, Feb 22, 2001 at 09:53:26PM +0100
X-mailer:	Pegasus Mail for Win32 (v3.12c)

On 24 Feb 2001, at 18:30, the Illustrious Christopher Faylor wrote:

> On Thu, Feb 22, 2001 at 09:53:26PM +0100, Corinna Vinschen wrote:
> >> I just thought of another problem though -- if I put together a
> >> distro tarball that contains symlinks, the dos paths will match MY
> >> system, and not the user's system.  Unless part of the postinstall
> >> script is to run fix-symlinks on the symlinks included in the
> >> installed package...
> >
> >No. Obviously not. Since Cygwin tar reads and saves the POSIX path in
> >the tarball, it is absolutely correctly recreated when unpacked on the
> >target system even when the links are absolute links, say
> >/usr/include/foo or alike.
> >
> >Consider - it's _not_ the *.lnk file which is saved in the tarball but
> >the attribute to be a symlink. You would be right in case of using
> >WinZip when creating an archive. But that's unfair because it's only a
> >native Windows tool...
> 
> I wonder how WinZip handles .lnk files anyway?  Does it just restore
> them "as is"?

	Depends on how you add the .lnk file to the archive.  This is what 
happened when I tested this.

Archiving:
	a) adding directly to a zip file using "Add to WinZip Archive", 
converts the .lnk file  to a .bat file (cygwin.lnk becomes cygwin.bat).
	b) Opening a WinZip archive, and then copying the .lnk file to the 
archive leaves the file as is (cygwin.lnk remains cygwin.lnk).

De-archiving:

	In a) above, when extracted using "extract" option, "cygwin.bat" stays 
"cygwin.bat".
	In b) above, when extracting using WinZip "extract" option, 
"cygwin.lnk" stays "cygwin.lnk" and may be launched normally.

	Peace,

		Paul G.


Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -