On Mon, Jun 28, 2010 at 05:16:05PM -0600, Eric Blake wrote: >On 06/28/2010 05:08 PM, Yaakov (Cygwin/X) wrote: >> It is not unusual for mono packages to create a wrapper script (to be >> installed in PATH) in the same directory as an assembly (which has .exe >> suffix and is installed out of PATH), which uncovered a regression using >> the 20100622 snapshot: >> >> echo script > foo >> echo executable > foo.exe >> mkdir bar >> install foo bar/foo > >The problem is here - should install be open()ing "foo" (the script) or >"foo.exe" (the executable) as the source file for copying into bar/foo? > Since it is never a good idea to have both an .exe and a script of the >same name in the same directory, is this really a regression, or just >bad behavior on mono's part? Remember, libtool was recently changed to >avoid exactly this ambiguity. Or should I be trying to patch coreutils >(and/or someone patch cygwin1.dll) to try harder to open the script >instead of the .exe when the suffix-less file conflicts with the .exe?
Is the dll "misbehaving" here or the install program? 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
