Closed Bug 679016 Opened 13 years ago Closed 13 years ago

Remove outdated Seamonkey Profile Migrator

Categories

(Firefox :: Migration, defect)

defect
Not set
minor

Tracking

()

RESOLVED FIXED
Firefox 9

People

(Reporter: marco, Assigned: marco)

References

Details

Attachments

(1 file, 1 obsolete file)

Remove nsNetscapeProfileMigratorBase.cpp and nsNetscapeProfileMigratorBase.h.
Move code needed by Seamonkey migrator into nsSeamonkeyProfileMigrator.cpp.
Attached patch Patch (obsolete) — Splinter Review
Attachment #553208 - Flags: review?(khuey)
Attachment #553208 - Flags: review?(benjamin)
Attachment #553208 - Flags: review?(gavin.sharp)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment on attachment 553208 [details] [diff] [review]
Patch

We don't all need to look at this.

I'll review it soon.
Attachment #553208 - Flags: review?(gavin.sharp)
Attachment #553208 - Flags: review?(benjamin)
Comment on attachment 553208 [details] [diff] [review]
Patch

I don't want to move all this code around.  We should get rid of it entirely (by killing the Seamonkey profile migrator).  If we're not willing to do that, then we should just leave it as is.
Attachment #553208 - Flags: review?(khuey) → review-
I'd like to remove the Seamonkey profile migrator, if I can. Who should decide about this?

Note that removing Seamonkey profile migrator, we can also remove libreg.
Summary: Remove Netscape Profile Migrator → Remove Seamonkey Profile Migrator
Based on the mork removal changes I suspect that migrator is really outdated, btw cc-ing Callek
(In reply to Marco Bonardo [:mak] from comment #5)
> Based on the mork removal changes I suspect that migrator is really
> outdated, btw cc-ing Callek

I bet the migrator is VERY outdated, that said I don't want to completely drop it. The ability to import from similar profiles is a big gain for both Firefox and SeaMonkey.

If it is decided (by Module Owner) that the current state of the migrator is bad enough that it must be removed, I'd like an "ok" to re-add it at a future date.

And of course, yes, Mork is outdated here, we have Places for Bookmarks and History now, and Sync support.
Does it actually import modern Seamonkey profiles though?  I would expect it's importing profiles from the suite days ... which isn't exactly useful.
Assignee: nobody → mar.castelluccio
It imports profiles from a file saved as a Windows registry file. It's completely different from Firefox and, most probably, modern Seamonkey.
(In reply to Marco Castelluccio from comment #8)
> It imports profiles from a file saved as a Windows registry file. It's
> completely different from Firefox and, most probably, modern Seamonkey.

Yes, I just dug through some code to check what it did exactly, and then with my local computer that never had an "old" suite installed.

And I can confirm with the supported Suite versions this is dead code. And *very* dead code at that. I'll support simply dropping it at that.
Summary: Remove Seamonkey Profile Migrator → Remove outdated Seamonkey Profile Migrator
Attachment #553208 - Attachment is obsolete: true
Attachment #553518 - Flags: review?(khuey)
Blocks: 679352
I need someone that could send this to tryserver, before the checkin.
Try run for b291507659ba is complete.
Detailed breakdown of the results available here:
    http://tbpl.allizom.org/?tree=Try&usebuildbot=1&rev=b291507659ba
Results (out of 229 total builds):
    success: 218
    warnings: 11
Builds available at http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/Ms2ger@gmail.com-b291507659ba
http://hg.mozilla.org/mozilla-central/rev/241af714f92d
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 9
Blocks: 706020
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: