Re: [Duplicity-talk] Version 0.6.0 Released - Checkpoint/Restart

[Richard L. Houston]

> Eric Evans wrote:
> > [ Kenneth Loafman ]
> >> The thing I realized before I finished this was that there needed
> to be
> >> some way to 'name' a backup set.  Right now, you can use an option
> like:
> >> --archive-dir=~/.duplicity/backup_name, but I'd like to move to
> the
> >> point where each backup had its own directory, located by name,
> with all
> >> the options stored in the directory along with the sig and
> manifest
> >> files, but then I took it another step.
> >>
> >> It would be handy to use a database for all of this, both the sig
> and
> >> manifest info could be stored in the database, along with options,
> logs,
> >> and history.  An SQL database could be used for this quite easily,
> but
> >> my issue with database access is that now you're into major
> program
> >> requirements that get away from small size.  

What about Sqllite, would that be small enough and portable enough? I think it 
has python bindings?

Thanks

Rich
Just a thougt, sorry to speek out of turn.