Upgrading firefox to firefox 3 -keeping plugins+bookmarks

[kasse]

I have tried to search for how to upgrade to the firefox 3 package while keeping the bookmarks and the plugins
I assume that you cannot simply keep the old copy of the .mozilla directory.
For the bookmarks I assume that you can export the bookmarks and import them in firefox 3.

[richardpl]

What are you talking about?
I have installed firefox3 and all my plugins+bookmarks are still there.
But note that many plugins are not yet supported in firefox3.

[kasse]

Thank you for your reply, so how would I go about to do it:

pkg_add -r firefox3

and then should I pkg_delete firefox-2.0.XXX

Would this keep my old $HOME/.mozilla folders, with all the plugins?

[richardpl]

Originally Posted by kasse

pkg_add -r firefox3

I used ports for that, but trying will not hurt.

Originally Posted by kasse

and then should I pkg_delete firefox-2.0.XXX

currently not required, but firefox3 vs firefox may not like
sharing of same ~/.mozilla directory.

Originally Posted by kassse

Would this keep my old $HOME/.mozilla folders, with all the plugins?

your home directory is actualy never touched by system utilities. I have ~/.openoffice.org2
but currently dont have openoffice installed.

[greencross]

On my system firefox2 & 3 coexist without any problem and share the same ~/.mozilla/firefox directory.
If you watch the ports tree you will see that firefox-3.0 and firefox-2.0.0.14 are presented as independent ports www/firefox and www/firefox3. They are executed by the following scripts: /usr/local/bin/firefox and /usr/local/bin/firefox3 respectively. Also portinstall or pkg_add put binaries into /usr/local/lib/firefox/ and /usr/local/lib/firefox3/ directories. So there is no danger of overwriting critical files.

[anomie]

In my case I used:
# pkg_delete -fx firefox

and then installed firefox3. Before firing up firefox3, I simply:
% mv ~/.mozilla ~/.mozilla.old

and finally launched firefox3 and imported the old bookmarks. All this extra work was probably unnecessary but I wanted to be sure I was starting with a "clean slate" with the new browser.

[drhowarddrfine]

All your bookmarks and "add-ons" (not the same as plugins) are retained in .mozilla/firefox/*.default. This is not deleted when you upgrade or uninstall.

[lumiwa]

Originally Posted by anomie

In my case I used:
# pkg_delete -fx firefox

and then installed firefox3. Before firing up firefox3, I simply:
% mv ~/.mozilla ~/.mozilla.old

and finally launched firefox3 and imported the old bookmarks. All this extra work was probably unnecessary but I wanted to be sure I was starting with a "clean slate" with the new browser.

Yes, Firefox 3 works and plugins too. But what you did with dependences? There are Gimp, Miro, Xine....and more...

[anomie]

@lumiwa:

> pkg_info -R -x firefox
Information for firefox-3.0_2,1:

Nothing requires firefox3 on my box. Can you explain more?

[lumiwa]

Originally Posted by anomie

@lumiwa:

> pkg_info -R -x firefox
Information for firefox-3.0_2,1:

Nothing requires firefox3 on my box. Can you explain more?

I have installed:
Gimp
Miro (I had)
KMplayer
Mplayer
ImageMagick
K3b
...
...
I forgot what was more...

When I deinstalled Firefox 2.014 there were complain about dependencies with the above applications. I ran portmaster --check-depends (transcode was too) and deleted those dependencies.
Miro for example has in Makefile aslo:
SE_PYTHON= yes
USE_GETTEXT= yes
USE_GNOME= glib20 gtk20 pygnomeextras
USE_GECKO= firefox seamonkey mozilla
USE_GSTREAMER= python
INSTALLS_EGGINFO= yes

Iwant to build with firefox. I changed firefox to firefox3 and portmaster wanted to install firefox3 but firefox3 is installed. Othervise Firefox3 is faster than 2 and for I have no problems.

[anomie]

@lumiwa: Maybe what you're describing warrants its own thread. Unfortunately (or, fortunately for me) I did not run into issues with imagemagick -> firefox or mplayer -> firefox dependencies. YMMV -- and obviously it does in this case. Sorry I can't help.

[lumiwa]

Originally Posted by anomie

@lumiwa: Maybe what you're describing warrants its own thread. Unfortunately (or, fortunately for me) I did not run into issues with imagemagick -> firefox or mplayer -> firefox dependencies. YMMV -- and obviously it does in this case. Sorry I can't help.

Thank you.
My suggestion is that should keep both versions or just 2. Othervise there are so many problems with dependencies. Like the last mplayer-plugin which need version 2.