[DragonFlyBSD - Bug #2527] Re: git: build: implement automatic world backups

[John Marino via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2527 has been updated by marino.


Yeah, given NFS scenario, AUTO_BACKUP should be redefinable.  It was defined as "=" before when it was assumed to be a local folder.

Tuxillo, the default "works".  There's a 100 ways to set up an NFS mount, nobody can guess them all.  The point is if somebody's particular setup works better with a different definition, they can set it.

Having an auto backup off when you don't even know it exists pretty much defeats the point.  By turning it off, you clearly know it exists and have made an informed decision.  It's erroring on the side of safety, aka it is the most conservative.
----------------------------------------
Bug #2527: Re: git: build: implement automatic world backups
http://bugs.dragonflybsd.org/issues/2527

Author: c.turner1
Status: In Progress
Priority: Normal
Assignee: 
Category: 
Target version: 


On 02/17/13 14:43, John Marino wrote:

>      Additionally, every time the "installworld" target is executed, the same
>      directories will be automatically backed up at the location of
>      ${MAKEOBJDIRPREFIX}/world_backup .  These directories could be restored
>      with the new make target "restoreworld-auto".

Bug: This breaks on NFS object trees as the copy tries to set flags,
which can't be done over NFS

Also,

1) getting an 'off button' back for this would be swell
2) build(7) should probably be updated with whatever the final result is.

personally, I'd prefer this was optional behavior with an 'on' switch,
(e.g. it seems sort of like a 'developer setting' like CFLAGS, etc)

but, that's me.

sorry to back seat drive with no attched patch - lifes a bit hectic ATM.

Cheers,

- Chris


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account