277488 - Create ReadMe.OS2 for Firefox/Thunderbird

Status: VERIFIED FIXED

Description

[Peter Weilbacher]

Now that we have an OS/2 specific readme file containing the most important
infos on this platform, we should try to produce a similar file for Firefox (and
Thunderbird), that takes into account the specifics there. The one
http://getfirefox.com/releases/ that is there at the moment only points to
<http://getfirefox.com/releases/> which doesn't help OS/2 users much.

Besides DLL conflicts the most important topic seems to be getting http links in
Thunderbird to open in Firefox and vice versa for mailto: links (->
ConfigApps/URL WPS objects). MOZILLA_HOME as a trick to let Firefox's import
routine find the Mozilla profile should also get mentioned. Anything else?

Comment 1

[Peter Weilbacher]

Created attachment 176399 [details]
README.os2 for Firefox

Comment 2

[Peter Weilbacher]

Created attachment 176400 [details]
README.os2 for Thunderbird

Almost the same file for Thunderbird. Am I right that Thunderbird interprets
the MOZILLA_HOME variable differently? On my system I set it to
MOZILLA_HOME=m:\ to get the Mozilla profiles in m:\Mozilla\Profiles and the
Firefox profile in m:\Mozilla\Firefox. For Thunderbird I then get it in
m:\Thunderbird... This looks like a bug to me...

With respect to the Seamonkey readme I added a section on the (three)
environment variables for OS/2 to both Aviary readmes. Anything important
missing or suggestions for better wording?

Comment 3

[Peter Weilbacher]

Created attachment 176401 [details] [diff] [review]
Makefile changes

This changes Makefile.in's for FF and TB so that the README.os2 files go into
mozilla\browser\locales\en-US\README.os2 and mozilla\mail\app\README.os2,
respectively, in the source tree.

Comment 4

[Steve Wendt]

I have no ability to change the flags on the attachments, but the readme files
look good to me.  Both readme files have this typo:
"By the default the installation routine"

Also, you might want to highlight this a bit more:
"If you migrate from Mozilla to <x> you might want to set MOZILLA_HOME so that
<x>'s import routine can find the existing Mozilla profiles."

I don't know if a whole subsection on migrating previous data is called for, but
perhaps rephrasing it slightly would work (this probably isn't perfect):
"If you are migrating from Mozilla, <x>'s import routine will only find the
existing Mozilla profile data if MOZILLA_HOME is correctly set to point to it."

Comment 5

[Mike Kaply [:mkaply] (on PTO until Nov 5)]

Steve - you have the power.

Comment 6

[Peter Weilbacher]

Created attachment 176629 [details]
Revised FF readme

Revised FF readme per stevew's comments. Carrying over his r+.

Comment 7

[Peter Weilbacher]

Created attachment 176632 [details]
Revised TB readme

Similarly revised readme for TB including what I took for a r+ from stevew.

Comment 8

[Peter Weilbacher]

Comment on attachment 176401 [details] [diff] [review]
Makefile changes

Mike, do you want me to revise this using cp instead of $(INSTALL) so that we
get a README.txt and not a README.os2 in the installation dir?

Comment 9

[Mike Kaply [:mkaply] (on PTO until Nov 5)]

I'll make the cp change when I check it in. Thanks for this awesome work.

Comment 10

[Peter Weilbacher]

Mike, do you require me to do anything or did you just not have time to check
this in yet?

Comment 11

[u29221]

No I'm just a slacker. We do need the rename, though like we did for Suite.

Comment 12

[u29221]

So looking at the existing readme.txt files, they are just bad. So we'll have
beetter files than everyone else? :)

Comment 13

[Peter Weilbacher]

Created attachment 184969 [details] [diff] [review]
Update to current makefiles, including renaming

These changes to the makefiles seem to do the trick with renaming. cp of course
only works if README_FILES contains only one file, I hope nobody gets the idea
to add another one and break this... Rich, is it possible to test this as well?
Mike, can you get this in or at least use for a "Deer Park" release if you do
one?

Yeah, FF and TB have more important problems on OS/2 but at least we get useful
readmes. :-)

Comment 14

[Rich Walsh]

Comment on attachment 184969 [details] [diff] [review]
Update to current makefiles, including renaming

WFM - review+

Comment 15

[Benjamin Smedberg]

Comment on attachment 184969 [details] [diff] [review]
Update to current makefiles, including renaming

This should really be in a subdirectory browser/locales/en-US/os2/README.txt so
that we can $(INSTALL) it with the other files.

Comment 16

[Peter Weilbacher]

Created attachment 190543 [details] [diff] [review]
Makefile changes with new subdir and $(INSTALL)

OK, this now works as Benjamin suggested if the OS/2 READMEs get checked in
into new subdirs {browser,mail}/locales/en-US/os2/README.txt.

Comment 17

[Mike Kaply [:mkaply] (on PTO until Nov 5)]

Done. finally.

Comment 18

[Peter Weilbacher]

Mike, did something go wrong with your checkins? In the nightly builds and when
I check out the readme.txt files every linebreak looks like 0d0d0a in hex so
that in normal OS/2 editors a blank line appears between all other lines (my vi
shows an extra ^M).

Comment 19

[Mike Kaply [:mkaply] (on PTO until Nov 5)]

Very strange. No idea what happened.

I did an OS22unix and rechecked them in - that should fix it.

Comment 20

[Peter Weilbacher]

Yes, that helped. Thanks.