Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 24 Feb 2001 18:30:09 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT]: Important change to symbolic link functionali ty Message-ID: <20010224183009.B6893@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <17B78BDF120BD411B70100500422FC6309E210@IIS000> <20010222184404.S908@cygbert.vinschen.de> <3A955952.6FF234D4@ece.gatech.edu> <20010222140454.F13561@redhat.com> <3A957332.FD98DFF6@ece.gatech.edu> <20010222215326.A908@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010222215326.A908@cygbert.vinschen.de>; from cygwin@cygwin.com on Thu, Feb 22, 2001 at 09:53:26PM +0100 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"? cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple