Re: Time machine does not save the build folder
Re: Time machine does not save the build folder
- Subject: Re: Time machine does not save the build folder
- From: turbo3d <email@hidden>
- Date: Thu, 6 Nov 2008 14:22:04 +0100
AH ! someone has understood my point !...
Le 6 nov. 08 à 14:14, Douglas Norton a écrit :
Hi,
I am with JP on this, until this thread I did not know that folders
could be excluded from Time Machine without being explicitly set
that way by me. I appreciate that backing up a builds folder is not
ideal, as it changes too often and can be recreated easily enough,
but I should be in control of the decision. It's the principle that
is the issue. It's my computer, not Apple's.
I would like Xcode to have a preference to enable this 'auto-
exclude' behavior, and better still when that preference is enabled
it should add the folders to Time Machine's exclude list so that I
have visibility on the excluded folders.
Now that this functionality is more widely known, I can foresee it
being abused by software designers who do not want parts of their
applications or data backed up for whatever reason.
Douglas
On Nov 6, 2008, at 3:58 , turbo3d wrote:
Hi guys,
thanks for help and advises.
My point was not to backup sources or abuse the build folder.
I use CVS and I backup regularly on many different devices,
outside TM.
My point was to have TM backup the various versions of my built
apps.
For me, a Build Product no longer belongs to XCode. It becomes
part of my thesaurus and I feel entitled to do what I want with
it, including TM backUp.
Nevertheless, as far as Build Product path is concerned :
In the build rules, you can place the built apps where you want
( build location / Per_configuration Build Product Path )
Nothing prevents you to choose a folder anywhere on any volume,
where you might very well have valuable data that are TM backed-up.
As soon as you do this, XCODE marks the folder to be excluded from
TM.
This behaviour is not documented and may lead to loss of data.
Eric Slosser gave the solution : add a run script to the build
phases that copies the built app ( and anything else you want to
be backed-up) in a TM enabled folder....
JP
Le 6 nov. 08 à 12:04, Hamish Allan a écrit :
On Thu, Nov 6, 2008 at 10:38 AM, turbo3d <email@hidden> wrote:
If I tell TM to backup a volume and it does not save all the
files and
folders of this volume, and that I dont know that this Backup
system may be
told ( in my back) to exclude some folders/files,
then this in not a backup system I can rely on.
You are right in a sense, but most people think the exception is a
good idea. Myself, I would prefer something more generic
(com.apple.TimeMachine.exclude rather than
com.apple.XCodeGenerated?)
The fact that you do not suggests, as others have pointed out, that
you are abusing the purpose of the build directory. So perhaps what
you see as an annoyance will encourage you to change your practices
for the better :)
There should not be any exception to a backup.
If a restor may cause problems to some applications
( XCode !!) then it is
during the restoration phase that some caution dialog may occur.
The point is that losing the build directory should never be a
problem
for XCode. It will simply be regenerated.
Why have you lost builds, anyway? Can you not simply use Time
Machine
to rewind the entire project directory to a particular point in
time,
and then rebuild?
Hamish
_______________________________________________
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