Marco Perez [:mpk] Reporter
	Description • 16 years ago

Compared to our other applications (e.g. SeaMonkey, Firefox, Sunbird) there is
no vendor value set for Thunderbird in application.ini . It would be nice if
"thunderbird -v" gave something along the lines of
 - Mozilla Thunderbird 3.0b1pre, Copyright (c) 1998-2008 mozilla.org
instead of
 -  Thunderbird 3.0b1pre, Copyright (c) 1998-2008 mozilla.org
(note the leading blank).

Caution: That change may also have an impact on the location of Thunderbird's
default profile (see bug 247973).

	Mark Banner (:standard8)
	Comment 1 • 16 years ago

Comment on attachment 341803 [details] [diff] [review]
Add "Vendor=Mozilla", patch for comm-central (trunk)

I'm jumping in here as a Thunderbird Dev, although I'm sure Benjamin would say the same.

Adding Vendor=Mozilla will change the profile location and that is unacceptable because everyone will loose their profiles.

Due to the various issues discussed in bug 424641 comment 21 we are currently unable to move our profile location and provide acceptable migration.

The only option may be to supply a Vendor of Mozilla, plus a Profile= option (see http://developer.mozilla.org/En/XUL_Application_Packaging), but I haven't looked at how that would affect things.

	Mark Banner (:standard8)
	Comment 2 • 16 years ago

(In reply to comment #1)
> The only option may be to supply a Vendor of Mozilla, plus a Profile= option
> (see http://developer.mozilla.org/En/XUL_Application_Packaging), but I haven't
> looked at how that would affect things.

Actually I don't think Profile would work, because on Mac, Thunderbird stores its data in ~/Library/Thunderbird as opposed to ~/Library/Application Support/Thunderbird - which is what it would be if you specified the Profile option (if I understand the documentation correctly).

Therefore I believe there isn't a way around this without of providing another option in application.ini and having toolkit support that.

	Marco Perez [:mpk] Reporter
	Comment 3 • 16 years ago

Hm, right. I agree with you that we can't let our users loose their profiles.
Should we mark this bug as being blocked by bug 424641?

	Mark Banner (:standard8)
	Comment 4 • 10 years ago

This is really just a duplicate of bug 247973, so we should just close this one out.