X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Eric Backus Subject: Re: symbolic link untar issue Date: Fri, 24 Aug 2007 20:24:59 +0000 (UTC) Lines: 16 Message-ID: References: <200708202358 DOT l7KNwl7b025934 AT tigris DOT pounder DOT sol DOT net> <46CADFAC DOT 4010209 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eric Blake byu.net> writes: > No, it is not an old-style link, because it has the .lnk suffix when > viewed via Windows. However, it is not a link that would normally be > created by the current coreutils, since I have added some .exe magic into > ln when symlinking against existing .exes: From this I guess that the .exe magic is currently in the code for each program that might create a symlink. Is there any way that the .exe magic could be moved to inside the symlink() function call, so that it automatically works for all programs that create symlinks? Or does that introduce other problems? -- Eric Backus -- 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/