On Sun, Mar 21, 2004 at 07:07:23AM -0800, Paul Heinlein wrote:Hi,
On Sat, 20 Mar 2004, Michal Jaegermann wrote:
Despite of a general policy of not changing versions this seems to me a correct thing to do here. Comments?
Red Hat issued a fairly major mozilla version bump (1.2 -> 1.4) last week, so my hunch is that backporting the latest patches was deemed unworkable.
This mozilla-1.4 and a matching galeon is what I am running right now on RH7.3 installations and spec patches I posted were for these new Red Hat releases. So far all "uninformed guinea pigs" :-) even failed to notice that anything has changed.
I fully expect that changes for RH8 are of the same order of magnitude and for 7.2 most likely too.
So I guess my comment is that there's probably not much choice...
The other choices as I see them are: - do nothing and hope for the best (it may work in majority of cases) - somebody with a good knowledge of mozilla sources, and a quite a bit of time to burn, digs through 1.4 sources and based on that fixes earlier stuff; sounds to me like a massive waste of effort.
Maybe somebody has some other options? There also can be some "gotchas" which I am missing. Hence my request for comments.
Michal
Here is some rain for the parade.
Because of internal pressure, mozilla is one of the things that I've always tried to keep current in our 7.3 based release. We currently have everything to mozilla 1.5, and will probrubly bump up again when mozilla 1.7 comes out. Anyway, because of that I've already ran into the problems.
So far, there are only three that I know of.
1st - galeon (of course)
2nd - nautilus-mozilla
3rd - evolution
The galeon problem is very obvious and straight forward, no real need to discuss.
The evolution problem will happen with a new user, after you've upgraded mozilla. I'm not positive it will happen, but it need to be checked.
To check it,
upgrade your mozilla.
Add a new user.
Log in as that new user and start up evolution.
If - you are able to so through the whole evolution startup without problems and elolution works correctly.
Then - the problem isn't there
Else - If at some point it complains about mozilla and won't work
You need to recompile evolution. It should get the right mozilla libraries
Fi
The nautilus-mozilla problem didn't get reported for a whole year, so it's really alot more subtle. Basically, the nautilus-mozilla rpm doesn't work. But as far as I can tell, the only time this really causes a problem is when GNOME users try to use their graphical help. It will fail.
To check it,
upgrade your mozilla.
Add a new user.
Log in as that new user and start a terminal window or nautilus.
From the 'Help' menu, select 'Contents'
If - The help starts up correctly
Then - the problem isn't there
ElseIf - You get some type of message saying that it couldn't open correctly
The bug is there.
Fi
I don't know if my solution is the best for everyone. I basically made a mozilla12 rpm, that had mozilla 1.2's libraries in it. Everything works fine with this. But, as I said, that might not be the best for everyone.
As I said earlier, this would be rather hard for me to check from a regular release, because I'v had mozilla replaced for a long time. But for people with a more plain redhat release, these checks really should be made so we can tell if they are problems that need to be addressed or not.
Troy
-- __________________________________________________ Troy Dawson dawson@xxxxxxxx (630)840-6468 Fermilab ComputingDivision/CSS CSI Group __________________________________________________
-- fedora-legacy-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-legacy-list
