Re: Re: Bug#237076: zinf: Zinf fails to start

On Tue, 09 Mar 2004 18:53:43 -0500, Sam Varshavchik  
<[email protected]> wrote:

> Kristian Kvilekval writes:
>
>> Remove ~/.zinf and restart.  I've seen this only when the metadatabase
>> (old style) gets corrupted.
>
> Being a survivor of several Zinf upgrades, I can tell you that with  
> pretty
> much every version of Zinf you need to blow away ~/.zinf, otherwise the  
> new
> version will be seriously fubared.
>
> Unless the upgrade path is stabilized, it's a good idea to have Zinf
> autorename ~/.zinf to ~/.zinf.save.$RANDOM if it does not recognize its
> current version.
>

This may not be the best idea, as if a user has saved playlists using the  
musicbrowser, by default they end up in ~/.zinf. If we just re-named  
~/.zinf a user would suddenly lose all their playlists, requiring them to  
go fiddling in ~/.zinf to get them back.

A less destructive way of doing this I feel would to rename specific files  
in ~/.zinf, without creating a new directory. So you could end up with  
~/.zinf/preferences.save.$RANDOM and ~/.zinf/db.save.$RANDOM which are  
normally the files that cause problems. This way, any other data in there  
like playlists will left in place.

This way the data lost from renaming files is possible to get back using  
just the UI (re-setting the prefs and rebuilding the db), the user dosn't  
have to fiddle about moving files around.

David

-- 
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click