Re: A change with the -n option for cp in Mac OS X 10.5
Re: A change with the -n option for cp in Mac OS X 10.5
- Subject: Re: A change with the -n option for cp in Mac OS X 10.5
- From: Eric Gorr <email@hidden>
- Date: Tue, 6 Nov 2007 09:26:25 -0500
| In case anyone else was using cp -n in their Run Script build phase, I thought I would post the answer I received here...
> I suppose it was #3. It looks like the exit status was changed due to > feedback that returning a zero exit status gives no way to determine > whether or not a file was actually copied (< rdar://problem/3624563>). > This is a divergence from the FreeBSD behavior in 10.4.10 (FreeBSD > introduced the non-standard -n flag). Because -n is non-standard[1], > I'd recommend against using it.
On Nov 5, 2007, at 2:06 PM, Eric Gorr wrote: Not sure if there is a more appropriate mailing list (if there is, please let me know), but since I am using cp -n in a Run Script build phase, I figured this was close enough.
In any case, under 10.4.10, when executing cp -n, cp would return an exit status of 0 if the file you told it to copy existed or not.
Under 10.5, cp will return an exit status of 1 if the file already exists and one uses the -n option.
I was just wondering if:
1. 10.4.10 had a bug
2. 10.5 has a bug
3. the definition of how the -n option is supposed to work has changed
It seems strange that cp would return an exit status of 1 now if the file already exists. After all, the command will do exactly what it is supposed to do and not copy the file.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden