Some attention needs to be paid to the way Netscape and Mozilla builds 
work with profiles created in one another. Presently, neither build 
works very well with each other's profiles, and there's too much manual 
manipulation required of the end user, not to mention too much voodoo 
guesswork about what is supposed to work right.

I propose that Mozilla and Netscape profiles be entirely separated. 
Neither should use profile files intended for the other.

That said, how can we make this convenient for the end user?

1. Mirror Mozilla and Netscape profiles. Each time a build is run, it 
checks for new or updated profiles of the other, and builds or updates 
its' own versions of them transparently to the end user, making any 
modifications necessary to produce profiles native to the respective 
build

2. Build mirroring functionality into the Profile Migrator

3. Do no profile mirroring whatsoever; treat profiles in different 
builds as totally separate.

Thoughts?

P.S.: Something also needs to be done to eliminate the need to trash 
profiles between Mozilla builds, even "milestones," which is necessary 
to avoid lots of crashes. Is there some log of changes made to default 
profiles in Mozilla that can be leveraged to build some kind of super 
Profile Migrator?


Reply via email to