Re: GNU IceCat 2.0.0.10-g1 and use with the alternate profile option

[rmyster]

On 12/3/07, Giuseppe Scrivano <address@hidden> wrote:
> In the 2.0.0.11-g1 packages I uploaded the `icecat' script you sent me
> some days ago is included.  I don't think there is still need of it
> after the patch to the C++ code or am I missing some advantages of
> having it?

I thought we do or did you find a way to get an executable icecat
script directly from compiling when including the nsBrowserApp.cpp
edit?  Is the icecat script in the icecat-2.0.0.11-g1-i386 tarball
from the compile or did you manually place it in there afterwards?

In all my test compiles, I was never able to get a functioning icecat
script directly from the compile when including the nsBrowserApp.cpp
changes.  In those cases, I had to replace each instance of
run-mozilla.sh with run-icecat.sh in the icecat script after
compiling.   The icecat script that was generated with just the
nsXREDirProvider.cpp patch ran ok without edits but the resulting
binary wouldn't run if firefox was also running or vice-versa.

My final working icecat-2.0.0.10-g1 test compile required a manual
edit of the icecat script to replace each instance of "run-mozilla.sh"
with "run-icecat.sh".  There may be a simpler solution like just
including a symbolic link but haven't explored that route.

There must be some other factors involved because while the latest
icecat-2.0.0.11-g1-i386 you just uploaded now runs simultaneously with
firefox and the older iceweasel-2.0.0.6-g1-i386, it wont run
simultaneously with an earlier icecat-2.0.0.10-g1-i386 compiled test
version which uses a  completely different profile location different
from the ~/.gnuzilla/icecat directory.   I was expecting each compiled
version to run independent of each other as long as they were compiled
to use different profile locations.

Anyhow,  the number of people who want to run multiple self-compiled
versions simultaneously is likely pretty low so not likely to get a
lot of bug reports. Since this version can run alongside firefox, it
covers the original problem. I haven't done any test compiles with the
new icecat-2.0.0.11 code yet but will try some variations to see if it
makes any difference.