This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: native symlink
- From: "Larry Hall (Cygwin Developers)" <lhall at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Wed, 27 Mar 2013 18:41:30 -0400
- Subject: Re: native symlink
- References: <20130327151656 dot GB5860 at calimero dot vinschen dot de> <80C3E267-F369-4FF3-A3FD-69A997FFC33B at mac dot com>
- Reply-to: cygwin-developers at cygwin dot com
On 3/27/2013 5:53 PM, James Gregurich wrote:
Why don't you add an API call and utility to actually convert an existing > cygwin symlink into a native symlink. I'll give you code that does the work.
Cygwin already reads and uses the native symlinks. you might as well provide
a way to create them.
The main list is really the right place to make Cygwin feature requests.
Patches to the DLL can go to cygwin-patches. Other code can go to the
main list as well.
As for why this hasn't been done before, some of it is just no one has
done it. But perhaps more importantly is the question of the benefit.
There are (non-Cygwin) tools already that support this. Also, since
native symlinks only work on NTFS, providing a utility to create them
opens us up to bug reports and questions about these limitations. In
addition, there will be questions about why yet another "symlink"
utility exists and when should it be used. But if you want to argue
for such a tool, please review the previous discussions in the email
archives (to make sure you're not covering the same ground again) and
bring up your proposal on the main list. Be prepared for a fight
(ah, "robust discussion" ;-) ) though.
--
Larry