This is the mail archive of the
mailing list for the Cygwin project.
Re: x86/ -> ./ symlink
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sat, 29 Jun 2013 13:59:08 -0400
- Subject: Re: x86/ -> ./ symlink
- References: <878v1zo0q6 dot fsf at Rainer dot invalid> <20130629080152 dot GU2378 at calimero dot vinschen dot de> <20130629164600 dot GA1479 at ednor dot casa dot cgf dot cx>
- Reply-to: cygwin-apps at cygwin dot com
On Sat, Jun 29, 2013 at 12:46:00PM -0400, Christopher Faylor wrote:
>On Sat, Jun 29, 2013 at 10:01:52AM +0200, Corinna Vinschen wrote:
>>On Jun 24 19:52, Achim Gratz wrote:
>>> May I suggest that this sort of link (and the similar one in
>>> cygwinports) has potential to break mirror scripts in bad ways? Not
>>> quite as bad, but linking x86_64 -> 64bit also results in duplicates
>>> that aren't serving a good purpose.
>>The x86 symlink break the "Install from directory" function of
>>setup.exe. It runs into some endless loop. If I remove the symlinks it
>>works as usual. I don't know why it does that at all. It has no
>>business reading these symlinks. If nobody beats me to it, I'll
>>investigate next week.
>Are you saying that this is happening with a CVS version of setup.exe?
>If not, it seems impossible that this symlink would cause an issue on a
>Or, maybe you're copying the whole release area to your work area as
>you proposed in the cygwin list.
I didn't try to duplicate this but I did just move the symlink down a
level. There are now x86 and x86_64 directories containing symlinks
to the respective release areas. That is what it should have looked
There are also setup.ini files in those directories but they are likely
to be stale.