Closed Bug 13305 Opened 21 years ago Closed 21 years ago

migrate the "mail.imap.root_dir", "news.directory", "mail.directory" prefs to the "mail.root.<type>" pref

Categories

(MailNews Core :: Backend, defect, P3)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sspitzer, Assigned: sspitzer)

References

Details

see related bug #11335

we also need to set the following pref to point to the directory with the newsrc
files:

"mail.newsrc.file.root" (or something else, I'm taking suggestions.)

on unix, that's either the old "news.directory" value, or ~.
everything else, its "news.directory" or PROFILE/News
Status: NEW → ASSIGNED
Target Milestone: M11
marking m11.

accepting
planning to check this in today, so alecf can use it.
FYI, changing "mail.newsrc.file.root" to "mail.newsrc_root"
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
fixed.

after migration, if the "mail.root.<type>" prefs are set, they are set to:

"mail.root.imap" == "mail.imap.root_dir"
"mail.root.nntp" == "news.directory" | $PROFILE/News
	"news.directory" if windows and mac, $PROFILE/News if UNIX.  In 4.x,
	"news.directory" pointed to the newsrc files, but the summary files were
	under ~/.netscape/xover-cache/<host>.  UNIX 5.0, its under
	$PROFILE/News, like the other plaftorms.
"mail.root.pop3" == "mail.directory"
"mail.root.none" == "mail.directory"
"mail.newsrc_root" == "news.directory"

note, these prefs may not be set.  example:  mail.root.pop3 isn't set if you
were using IMAP in 4.x

mail.root.none and mail.root.imap aren't set it if you used imap in 4.x

the gaping whole here is what happens if the user didn't migrate?  where to
"mail.root.<type>" and "mail.newsrc_root" get their values from?

alecf is taking care of that. see bug #11335.
QA Contact: lchiang → laurel
Status: RESOLVED → VERIFIED
Appears to be migrating ok using:
1999-11-09-11m11 NT 4.0
1999-11-09-11m11 linux 6.0
1999-11-08-08m11 mac OS 8.5.1
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.