383052 - FF needs an additional migrator option for new SMv2.0 (a.k.a. suiterunner)

Status: RESOLVED WONTFIX

(Firefox :: Migration, enhancement)

Description

[Serge Gautherie (:sgautherie)]

I did not test it myself,
but Mark (and I) think FireFox and Thunderbird should be affected too.

See bug 383051.

(IRC)
Mark:
{{
FF & TB have got away with it in their migrators because SM has used registry.dat up until now....

oh, they won't work with the suiterunner one
for two reasons, they don't work with profiles.ini, and secondly they won't have the extra mozilla.org/SeaMonkey to the profile location

I'm waiting to see how long it takes them to realise that now we've switched on trunk ;-)
}}

I choose to let you know right away ;->

Comment 1

[Serge Gautherie (:sgautherie)]

What I'm wondering is if the detection/"reading" part of the migrator could be (code) shared between all toolkit apps ? (at least between SMv2 and FF/TB of course.)

I understand the migration/"writing" part details are specific to each app.

Comment 2

[Mark Banner (:standard8)]

(In reply to comment #0)
> oh, they won't work with the suiterunner one
> for two reasons, they don't work with profiles.ini, and secondly they won't
> have the extra mozilla.org/SeaMonkey to the profile location

There's now a patch on bug 383052 to detect the profiles.ini waiting review. Obviously FF/TB will possibly want to change some of the migrators now that SeaMonkey has switch various components to the toolkit back-end.

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)
> There's now a patch on bug 383052 to detect the profiles.ini waiting review.

(Mark meant bug 383051.)

Comment 4

[Mark Banner (:standard8)]

I've just raised bug 462147 for the TB profile migration code. So this is now Firefox only.