Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: Andrew Schulman <andrex AT alumni DOT utexas DOT net>
Subject: Re: [ANNOUNCEMENT] New package: stow
To: cygwin AT cygwin DOT com
User-Agent: 40tude_Dialog/2.0.15.1 (b106d0fd.130.289)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
References: <20050517090007 DOT 762DF6D41F6 AT calimero DOT vinschen DOT de> <4289C0C5 DOT 70103 AT atomice DOT net>
Date: Wed, 18 May 2005 14:41:53 -0400
Message-ID: <wxohi360e2l7$.oa6zsuxipz2z$.dlg@40tude.net>
In-Reply-To: <4289C0C5.70103@atomice.net>
X-Archive: Yes

> Does stow have support for hard links at all?

No, not at present.

> If not is that an easy 
> thing to add in?

It probably is, although I can't spend any time on it in the foreseeable 
future.  

>  Such an option would make stow more useful on Cygwin, IMHO.

I think you're right, for the following reasons.

One, as I said in the announcement, Cygwin implements symlinks as 
Windows shortcuts, which are broken.  Therefore, stow will only be 
useful for installing software that is used exclusively within Cygwin 
(which interprets the shortcuts to emulate POSIX behavior) and that 
doesn't install any DLLs (since Windows won't interpret the symlinks 
correctly).

Two, Cygwin implements hard links as file copies.  Windows file systems 
don't support hard links, so this is probably the best that can be done.  
So 'ln a b' is really the same as 'cp -p a b'.

Now that approach has obvious disadvantages (it uses twice the disk 
space; changes in either file aren't reflected in the other, since 
they're different files), but for software installation it would have 
the advantage of solving the symlink problem.  Installed files 
(including DLLs) would just be copied into the installation directory, 
where Windows can use them.  The original, stowed copy (e.g. 
/usr/local/stow/emacs) would become superfluous, except as a map of 
which files to delete if you want to uninstall the package.  Also, the 
problem of modifications to the target not being reflected in the source 
probably isn't very important for software installation, since the 
package files don't get changed much.

So, if someone wanted to pursue this, I think it would be useful.
Andrew.

--
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/