On 06/08/2010 09:42 AM, [email protected] wrote: > As to the "cp" issue, while IMHO, it should go ahead and do the copy, > a more instructive error message would be helpful: > > cp: cannot create regular file `my': File 'my.exe' exists
Huh? Do the copy, then give a failure message? No. A failure message should only occur if the copy failed. Did you mean "continue to fail, but make the failure message more friendly?" If so: Patches to coreutils welcome. But be aware that this error message uses the equivalent of perror(), where EEXIST would not have quite that wording. In other words, such a patch would be pretty invasive, to recognize the exact errno value that cygwin1.dll returns in this particular failure-to-create case, then massaging just that error case into your desired message, so I probably won't be writing the patch any time soon (I've got higher-priority things on my plate at the moment). Or did you mean "change it to succeed, in spite of the naming conflict", in which case there is no failure message and nothing to patch in coreutils. -- Eric Blake [email protected] +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
