Re: xcodebuild Messing with Time Machine [Details Exposed]
Re: xcodebuild Messing with Time Machine [Details Exposed]
- Subject: Re: xcodebuild Messing with Time Machine [Details Exposed]
- From: Jerry Krinock <email@hidden>
- Date: Tue, 05 Aug 2014 15:03:49 -0700
On 2014 Aug 05, at 08:59, Jens Alfke <email@hidden> wrote:
> That sounds desirable to me, because build output is (a) large, (b) rapidly changing, and (c) not worth backing up because it can easily be recreated.
>
> I guess my underlying question is: why do you want your build directories to be backed up?
Thank you, Jens. Good question. Indeed, I don’t need that intermediate build garbage. The problem I saw was that xcodebuild was putting its Time Machine exclusions not only upon the specified intermediate build directory, but upon other directories as well.
You motivated me to run an experiment and see if this is reproducible. It is, and now I’ve identified the bug exactly.
The bug is that the Time Machine exclusions are being installed not only on the specified intermediate builds directory, but on the *parent* directory of this directory as well.
Since this requires some big screenshots to show, I’ve dusted off my blog.
http://www.sheepsystems.com/developers_blog/xcode-vs-time-machine.html
and also filed it as Apple Bug 17922437.
> If you want archives of previous releases of an app, you can just copy the app itself (without the squigabytes of intermediate files) to some other archive directory
Yes, I thought I was doing that! The trouble was that my supposed archive directory was another subdirectory of that same parent folder on which Xcode is incorrectly placing Time Machine exclusions. Now that I understand what it’s doing, I can work around it.
_______________________________________________
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