Yes, that seems the right way to do it. Thanks!

-- 
Rick Mann
rm...@latencyzero.com

> On Jun 27, 2017, at 16:07, Charles Srstka <cocoa...@charlessoft.com> wrote:
> 
>>> On Jun 27, 2017, at 4:45 PM, Rick Mann <rm...@latencyzero.com> wrote:
>>> 
>>> 
>>>> On Jun 27, 2017, at 14:30 , Charles Srstka <cocoa...@charlessoft.com> 
>>>> wrote:
>>>> 
>>>> On Jun 27, 2017, at 4:17 PM, Rick Mann <rm...@latencyzero.com> wrote:
>>>> 
>>>> Thanks for that, Charles!
>>>> 
>>>> I wasn't sure because of the existence of the clonefile() call in 
>>>> <sys/clonefile.h>, implying that operation was different from copyfile(), 
>>>> but looking more closely at the sample code, I see that you can call 
>>>> copyfile() with COPYFILE_CLONE, which seems like it will clone if possible 
>>>> and copy if not.
>>>> 
>>>> But there didn't seem to be equivalent calls in NSFileManager, hence my 
>>>> question.
>>> 
>>> Apple clearly wants the clone feature to get used. :-) The ability to do a 
>>> copy the old way is still there if you drop down to C, but since I can’t 
>>> think of too many reasons to want to do that, it makes sense to leave it 
>>> out of the high-level API.
>> 
>> Agreed. Thanks for the code, and for showing the other techniques. In my 
>> case, I still have to support HFS+, and I want to do that with hard links. I 
>> wish there was an API to clone-or-hardlink, but I can do that.
> 
> That should be easy enough to do. One thing I’d recommend would be checking 
> the volumeSupportsFileCloningKey key on URLResourceValues, rather than 
> checking the file system type itself. That way, if APFS gets supplanted by 
> some even better file system in the future, you’ll already support it.
> 
> Charles
> 
_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to