traverso-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Traverso-devel] Incremental backup solution


From: Jonatan Liljedahl
Subject: Re: [Traverso-devel] Incremental backup solution
Date: Wed, 03 Oct 2007 22:26:55 +0200
User-agent: Thunderbird 1.5.0.4 (X11/20060516)

Remon wrote:
> Hi,
> 
>> Is the backup done only on the XML file or on the audio sources too?
> 
> Only on the xml file, running it on the audiosources isn't very usefull, they 
> don't change (and if they do, the backup will take very long to finish...)

Ok, they don't change because any changes creates new audiosources?
If so, then there's the problem with cleaning up (removing) unused
audiosources. (which is a feature much needed but not yet existing I
think?) Only looking at the current project file for unused audio might
remove audiosources used in a backup. But if it could be smart enough to
look at each rollback and indicate if any rollback would be destroyed if
a certain audiosource is removed? Or perhaps the other way around, one
could tell it to clean up audiosources unused in the current project and
N backups back in time!

>> I really don't think you should depend on Python. If you still choose to
>> use rdiff-backup, make sure it's optional (if no python is installed,
>> disable the feature).
> 
> It will not be a dependency at all, if the program isn't installed, the 
> backup 
> solution will not be available/shown.
> Python is installed on many systems, but for those where it isn't installed 
> it's indeed a huge 'dependency'.
> So a similar program that doesn't depend on python would be favorable....

Yes, if we could find C/C++ source for the same task it could be
integrated into traverso.
How big is a common XML project file? If it's not too big, then why not
just back up the whole file instead of using incremental diff backup?

-- 
/Jonatan         [ http://kymatica.com ]




reply via email to

[Prev in Thread] Current Thread [Next in Thread]