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

[rmyster]

On 11/30/07, Giuseppe Scrivano <address@hidden> wrote:
>
> Can you please send me directly your file?
>

Previously sent in a separate message.

> Are you sure you have your profiles in ~/.mozilla/firefox?  In the
> .mozconfig file we are using to compile it, there is specified:
> ac_add_options --with-user-appdir=.gnuzilla.  I have this directory
> with profile information, can you check if it is present on your
> machine too?
>

I'm sure that the icecat-2.0.0.10-g1 version creates new profiles in
~/.mozilla/firefox and it writes the new entries to
~/.mozilla/firefox/profiles.ini.  When I create new profiles with the
earlier iceweasel-2.0.0.6-g2 version, it creates new profile folders
in ~/.gnu/iceweasel(created the first time  iceweasel-2.0.0.6-g2 ran)
and writes those entries to ~/.gnu/iceweasel/profiles.ini.  If I
rename/delete the existing .mozilla folder, a new one is created when
icecat-2.0.0.10-g1 starts up.

When iceweasel-2.0.0.6-g2 was first started, it did create a .gnuzilla
folder but I've never seen anything in it.  icecat-2.0.0.10-g1 just
defaulted to using the ~/.mozilla/firefox default profile instead of
the profiles in ~/.gnu/iceweasel as I was expecting like the earlier
2.0.0.6 version.

I do run both firefox and iceweasel independently of each other but
since they are separate installations and use separate profile
folders, there wasn't previously any problem. The main reason for both
is to allow plugins for some profiles and none for others.  Since all
the plugins seem to get shared between profiles, running a separate
installation with no plugins added allows this although the behavior
exhibited by the latest icecat-2.0.0.10-g1 would sort of remove the
reason for running both side by side.

Note: All references to behavior mentioned above is based on tarballs
downloaded directly from http://gnuzilla.gnu.org/download/, not
personally compiled versions.

> > Is the creation and use of the ~/.gnu/icecat profile folder equivalent
> > something that can be accomplished without recompiling? If not, could
> > you point me to parameters or  source code sections which affects
> > this?  Thanks.
>
> As I said you, this value was specified at compile time.  I don't know
> if it is possible to choose another one at run time but I don't since
> this location contains files used by Firefox/IceCat at startup.

Are you saying that the "ac_add_options --with-user-appdir=.gnuzilla"
entry is what specifies the location of the profile directory? If so,
it doesn't seem to work in either the iceweasel-2.0.0.6-g2 or the
icecat-2.0.0.10-g1 version.  The .gnuzilla directory is created with
both versions but it isn't used for anything -- at least not on my
system. I couldn't figure out how the iceweasel-2.0.0.6-g2 version
created the ~/gnu/iceweasel profile directory and that was why I
asked.  I've tried compiling several different variations of
icecat-2.0.0.10-g1-i386 but have not been able to duplicate the
profile behavior of what was present in iceweasel-2.0.0.6-g2-i386.