Date: Fri, 28 Aug 2009 01:36:05 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin, symlinks, and wine
Message-ID: <20090828053605.GA23501@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <a71bd89a0908272152x64b1dd85vf62e99b8829dcd20 AT mail DOT gmail DOT com>  <20090828053111 DOT GA22638 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090828053111.GA22638@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Fri, Aug 28, 2009 at 01:31:11AM -0400, Christopher Faylor wrote:
>On Thu, Aug 27, 2009 at 09:52:26PM -0700, Dan Kegel wrote:
>>Although it seems strange to run cygwin on top of wine, doing so would
>>make it possible to run a lot of build scripts for windows apps
>>unchanged, which would be very handy in verifying that wine works
>>properly (see http://wiki.winehq.org/UnitTestSuites ).
>>
>>The problem is, wine doesn't support the system attribute on files
>>well.
>
>The system attribute isn't needed for the .lnk type of symlink that
>you're talking about.  The file just has to be read-only.  So something
>else is wrong.

Ah, sorry.  I take that back.  I didn't read the whole bug report.

These *are* the system-style symlinks, probably created by setup.exe.
Changing them to .lnk type should fix that problem.  Why not just write
some sort of converter script to do that?

Regardless, the comment about a patch still holds despite the code
offered in the wine bug report.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple